Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 095 / pcb90doc.arc / PCBOARD.DOC

Wrap

Text File | 1985-12-22 | 193.4 KB | 4,277 lines

***************************************** * * * PCBoard Documentation - Ver. 9.0 * * December 22, 1985 * * * * by * * * * Clark Development Company, Inc. * * P.O. Box 71365 * * Murray, Utah 84107 * * (801) 266-0328 * * (801) 266-0329 * * (C) Copyright 1985 * * All Rights Reserved * * * ***************************************** T A B L E O F C O N T E N T S ----------------------------------- Chapter 1 - Introduction Chapter 2 - Distribution Guidelines Chapter 3 - Hardware Required Chapter 4 - Modem Switch Settings Chapter 5 - Getting Started Chapter 6 - Configuring PCBoard Chapter 7 - Configuring Conferences Chapter 8 - Establishing Download Security Chapter 9 - Establishing User Time Allotments Chapter 10 - Script Questionnaire Files Chapter 11 - Call Waiting Menu Operation Chapter 12 - Sysop Function Key Assignments Chapter 13 - Program Menu Selections Chapter 14 - Tips on Running the Board Chapter 15 - Questions and Answers Chapter 16 - File Formats Used PCBoard Chapter 1 December 22, 1985 I N T R O D U C T I O N ----------------------- PCBoard - Bulletin Board Software Clark Development Co., Inc. (C) 1985 (All Rights Reserved) Fred Clark, David Terry, Dave Staehlin P.O. Box 71365, Murray, UT 84107 (801) 266-0328 (801) 266-0329 This program is the end result of a dedicated group of sysops who saw the need for an alternative form of remote bulletin board software for the IBM PC/XT/AT family of computers. Due to their efforts, time, phone expense, and total co-operation with the authors, PCBoard has matured into the very comprehensive public domain remote bulletin board program it is today. This software is dedicated to all sysops who have contributed to it's development ... Because CPC12-xx RBBS code had grown beyond the needs of many BBS system operators - including extensive networking support, etc. - it was decided to write this code, using ideas gained from experience with RBBS and FIDO software. This product is the end result of those efforts. In some aspects it is more flexible than RBBS. Likewise, it lacks some features of RBBS which may be of need to a given bulletin board operation. If you are considering running this code, please look over the accompanying documentation carefully before trying to set up a system using PCBoard software - it may not meet your needs. The philosophy behind PCBoard is the following: 1. Quick running to minimize wasted user time on system. 2. Single node operation. 3. User friendliness. 4. Minimum time to get into system. 5. Increased protocol support. 6. Single user menu. 7. Additional Sysop support. With these above items as a goal, PCBoard was developed using ideas from RBBS, FIDO, and CP/M based software into the code. With the release of the new Quick BASIC (tm) MicroSoft 2.0 compiler, is was possible to incorporate additional features in the program which improved it's operation substantially. The current product requires the use of the Quick BASIC compiler (or equivalent) for converting the source code to an executable file. In order to include the additional features desired in the program, it has been necessary to 'split out' portions of the code into separate relocatable code segments - allowing the code to exceed the 64K limit of physical basic code space. Because of the complexity of the code, the source code will remain the property of Clark Development Co, Inc. and it (the source code) will not be made available to the general public. 1 - 1 PCBoard Chapter 2 December 22, 1985 D I S T R I B U T I O N G U I D E L I N E S ---------------------------------------------- This code is released under the following guidelines: 1. The software is copyrighted by Clark Development Co., Inc. and may not be sold for profit by anyone. The executable version of the program - PCBOARD.EXE - is available to all who desire a copy and should be freely distributed. The source code however, remains the property of Clark Development Company, Inc. - with all rights reserved. 2. If you are a sysop using this code for your private use, we do not request a donation. However, if you are a business, municipality, etc. and are using this code for business use because of the additional security levels available inside conferencing, etc, we do ask for a $50.00 donation to help offset the cost of maintaining and distributing this code for your use. Please send all donations to: Fred Clark Clark Development Co, Inc. P.O. Box 71365 Murray, Utah 84107 We will return to you a paid invoice in the amount of your check for tax purposes. If desired, we will also include a disk of the most current version of the product - including all accompanying documentation. 3. The assembly language linkable file used by PCBoard is copyrighted by David Terry, Sysop - Salt Air BBS, Salt Lake City, UT, and may not be used or modified without his written consent. Extra special thanks to Dave Staehlin, Sysop TBC BBS, Albuquerque, NM (505) 821-7379 (and his understanding wife Cindy) for his outstanding assistance in modifying the ANSI.SYS driver for use with this code, for his expertise in providing the means of allowing the sysop to return to the program after exiting to DOS from remote, for devising the system of relocatable code segments, and for his unending patience in dealing with the code's author. 4. Because of the similarity of functions between RBBS code and PCBoard, there may be a tendency to direct questions concerning PCBoard's operation to the author's of CPC RBBS code. Please, DO NOT request assistance on this code from them. They DO NOT have the source code and can not answer your questions. 5. This code may not be distributed in modified format to anyone! 6. The latest version of the software can always be obtained from either the Salt Air BBS public board at (801) 266-0328 for registered Salt Air board users, from the Salt Air BBS PCBoard sysop's only board at (801) 266-0329 for registered PCBoard sysops, or from the TBC BBS at (505) 821-7379. All boards support 2400 baud. Numerous other boards around the U.S. also have the code available for downloading. 2 - 1 PCBoard Chapter 2 December 22, 1985 NOTE: We will not respond to questions concerning how to configure your system in order to run PCBoard software, nor will we respond to any questions you may have during your initial installation prior to getting PCBoard up and running. This software has been tested to run under various drive configurations and program settings. If your software does not run - it is probably not due to a program error - but rather your configuration setup. Because of the extreme difficulty in trying to respond to configuration and/or setup questions through this board's message system, we will not respond to any questions of this nature. If you leave us either a message or comment requesting assistance in setting up your system to run PCBoard, we will delete the message and no response will be made. We are sorry to have to enforce this policy. However, if we did not, we would be on the phone or board continuously for the next 5 months answering questions. If you are unable to get this software to run, we suggest you contact another sysop who is running the code for possible assistance. We will only respond to documented 'Bugs' which are reported to us after your board is up and running. To document a problem, you must provide the following in the form of an upload file: 1. A step-by-step description of the problem - including the keystrokes made. 2. The portion of your CALLER file showing the entire user session of the caller(s) who experienced the problem. 3. Your name, board's name, and a voice phone number where we may contact you for further information if we need it. If you fail to provide this information, we will not respond to your question. Also, we will usually not acknowledge messages left which ask for this and that to be added to the code. We will keep your requests on file for possible future enhancements, but will not issue an immediate reply to your request. Please understand that this code can not be all things to all sysops. We have tried to include the items we felt were most needed for boards that cater primarily to the adult business community. We appreciate your suggestions. However, we intend to implement very few future changes to the code. For example, this code does not support a 'ring-back' feature. It is assumed a board running this code is always available to their users without having to call back. Similarly, only callers at N,8,1 modem settings are allowed access into the program. This is because callers at E,7,1 settings can not use the Xmodem, CRC Xmodem or Ymodem CRC capabilities of the program. The code will function under most multi-tasking softwares where the sysop wishes to perform other functions in the partition opposite the board's. It is NOT recommended that multiple copies of the software be run concurrently using mutil-tasking software however. There is no support in this code for multi-node support. This code was not designed to be used by a novice sysop who is setting up a remote bulletin board service for the first time. If you are not thoroughly familiar with hard disks, subdirectories, paths, etc., we do not recommend that you try running this code. It is suggested that this code only be run on a hard disk system because of the large number of files which are needed to support it - and the size to which these file can grow. 2 - 2 PCBoard Chapter 2 December 22, 1985 Please Note: This software does not support NULLS and it ALWAYS sends a line feed! If your callers must have NULLS, or can not live with forced line feeds - this code is not for you... 2 - 3 PCBoard Chapter 3 December 22, 1985 H A R D W A R E R E Q U I R E D ---------------------------------- In order to run this software, you will need the following: 1. An IBM PC/XT/AT or equivalent with a minimum of 256K of memory. 2. A hard disk of sufficient size to support the large number of program and user downloadable files. 3. A "smart" modem capable of sending verbose results to the software to indicate the speed at which a caller logs on. (i.e. The modem MUST be able to respond with CONNECT, CONNECT 1200, and CONNECT 2400). If your modem will not send the above result codes to the software at the time a user logs on, the program will not function. 4. A modem-to-PC cable which has ALL RS-232 pins "active". If your cable and/or modem does not support all the RS-232 pins, the software will not function. This is usually indicated by the inability of the program to either answer or hang-up the phone. 5. The file ANSI.SYS "loaded" on your machine from the CONFIG.SYS file at the time of initial boot-up. If you do not have the program ANSI.SYS (or it's equivalent) active, you can not operate this code under "graphics" mode. The code can be run without the ANSI driver loaded - however, the code will not support color graphics under that configuration. 3 - 1 PCBoard Chapter 4 December 22, 1985 M O D E M S W I T C H S E T T I N G S ------------------------------------------- Listed below are some common modem switch settings needed to run PCBoard code properly .... Hayes 1200 Baud External Modem ------------------------------ ----------------Switches-------------- 1 2 3 4 5 6 7 8 --- --- --- --- --- --- --- --- U U D D D U U D Switch 1 = DTR false (controlled by program) Switch 2 = Full result words sent (i.e. CONNECT 1200) Switch 3 = Result codes sent back to computer Switch 4 = Commands are not echoed back to computer Switch 5 = Auto answer is off. (controlled by program) Switch 6 = Carrier detect is off. (controlled by program) Switch 7 = Normal phone jack configuration Switch 8 = Enables modem to recognize commands U.S. Robotics Courier 2400 Baud External Modem ---------------------------------------------- --------------------Switches------------------- 1 2 3 4 5 6 7 8 9 10 --- --- --- --- --- --- --- --- --- --- U U D D D U U D U U Switch 1 = DTR false (controlled by program) Switch 2 = Full result words sent (i.e. CONNECT 1200) Switch 3 = Result codes sent back to computer Switch 4 = Commands are not echoed back to computer Switch 5 = Auto answer is off. (controlled by program) Switch 6 = Carrier detect is off. (controlled by program) Switch 7 = Normal phone jack configuration Switch 8 = Use normal "AT" command set. Switch 9 = Disconnect with +++ Switch 10= Not used Hayes 2400 Baud External Modem ------------------------------ The Hayes 2400 baud external modem does not used DIP switch settings. Instead, it's "DIP" settings are stored in nonvolatile memory in the modem. These settings are not lost - even after turning off the power to the modem. Once the modem has been initialized using the instructions given here, it will not be necessary to re-configure the modem again. It will work with all communications programs for the PC once this initialization procedure has been done. To configure the Hayes 2400, type in the basic program which follows and then "run" it to write the configuration into the Hayes' 2400 internal memory. Prior to actually running the program below, be sure your 4 - 1 PCBoard Chapter 4 December 22, 1985 modem is set to the original factory settings. If in doubt, first send the modem the string "AT&F&W" in a program similar to that below before configuring the modem. Please note that you must wait 2 seconds between the "AT&F&W" command and the command indicated below if you combine them into one program. 10 CLOSE 1 20 OPEN "COM1:2400,N,8,1,RS,CD,DS" AS #1 30 PRINT #1,"AT&C1&D2&T5E0&W" 40 CLOSE 50 END This will then allow your modem to be "controlled" by your software - rather than having the modem "force" itself on the code. The meanings of the above commands are: AT = Modem Attention Command &C1 = Software controls Carrier Detect &D2 = Software controls DTR &T5 = Prevents callers from initiating remote loopback test E0 = Do not echo modem commands to software &W = Write these changes to the Hayes' permanent memory By initializing the modem with these commands, the normal PCBoard modem commands will work - plus the Hayes will now work with all other PC communications software. All Other Modems ---------------- All other "smart" modems should use similar switch settings. The two critical ones are that the modem switches must NOT be set so that Carrier Detect (CD) and Data Terminal Ready (DTR) are "true" all the time. They MUST be set to "false" so that the software can control them and answer/hang-up the phone properly. The biggest problem most users have with their modems is failure to properly configure these two switches. The second biggest problem is failure to have all of the necessary RS-232 pins active as required - including pins 20 and 22. Finally, make sure your modem is capable of sending back the words "CONNECT, CONNECT 1200" and "CONNECT 2400" (if you are using a 2400 baud modem). If your modem is not properly configured to return these codes to the software, the program will not properly answer the phone and let the caller log on. 4 - 2 PCBoard Chapter 5 December 22, 1985 G E T T I N G S T A R T E D ------------------------------ PCBoard was designed to take advantage of the many benefits of DOS 2.0 and higher - including the use of subdirectories. As a result, new sysops setting up this code should carefully study this documentation before trying to run the program. It is essential that you outline your hardware configuration and file security PRIOR to actually running the code. Failure to properly configure your system and PCBoard data files in accordance with the guidelines presented can result in many long hours of frustration in trying to get the program to function properly. Even with advance planning, we recommend you plan on spending a MINIMUM of 4-6 hours for the initial setup and/or conversion from your current board's software. NOTE: Many files indicated herein have the letter "G" suffixed to their file name. This indicates a color graphics version of the main file being discussed and MUST be present for your color graphics callers. These files contain the chr$(27)+"[xxm" ANSI.SYS escape codes needed to generate color on your and the caller's machines. CAUTION: YOU MUST HAVE THE PROGRAM ANSI.SYS LOADED ON YOUR MACHINE BEFORE RUNNING PCBoard IF YOU INTEND TO SUPPORT COLOR GRAPHICS FILES!! TO INITIALIZE IT, PLACE A STATEMENT IN YOUR CONFIG.SYS FILE WHICH READS... device=<location\location>ansi.sys IF YOU DON'T UNDERSTAND THIS COMMAND AND THE USE OF DEVICE DRIVERS, WE SUGGEST YOU DO NOT TRY AND RUN THIS CODE!! IT IS NOT FOR THE NOVICE SYSOP!! When building or editing the "G" files, you should use the DOS color escape codes listed in your DOS 2.1 or higher technical reference manual. Please note that this software does not support 'music'. Throughout the code, several drive\subdirectory notations are made as to where specific files should be placed. They are: DEFAULT MAIN GEN HELP <SYSOPS Conference> These names are not hardcoded into the program! They are examples only of the names that can be used. Optionally, you can choose to make all of these locations one logical drive. However, in so doing you give up many of the built-in security features the program provides. For example, let's assume you have a single hard disk (drive C:), on which you wish to install the program. 5 - 1 PCBoard Chapter 5 December 22, 1985 Using the names above, and assuming you have one conference called SYSOPS, a sample configuration might be as follows: Drive C:\ (Root) | (Subdirectories) | +-----+------+------+---+--------------+ | | | | | Lotus WP dBase etc C:\PCBOARD (Default) Sub Sub Sub | BOARD.BAT PCBOARD.EXE PCBOARD.DAT REMOTE.SYS EVENT.SYS WATCHDG1.COM (All below would be C:\PCBOARD\+name) | +-------+------------+--------+-------+----------+-------+-------+ | | | | | | | | UP MAIN GEN HELP SYSOPS DL1 DL2 DL3 | | | | | | | | Files MSGS BLT HLPA SBLT Files Files Files Uploaded FSEC BLTG thru SBLTG for for for to PWRD BLTxx HLPZ SBLTxx Down Down Down Main TCAN DIR SDIR Load Load Load Board CNAMES DIRG SDIRG CALLERS DIRxx SDIRxx COMMENTS CNFN SYSOPS NEWASK.DAT CNFNG PRIVATES NEWREG.DAT PRIVATE SASK.DAT ASK.DAT WELCOME SANSWER.DAT ANSWER.DAT WELCOMEG SNEWS DOWNLOAD.TXT NEWUSER SNEWSG NEWS Files NEWSG Uploaded BRDM to BRDMG Sysops BRDS Conf. BRDSG The file(s) indicated in each location represent the files discussed later in this document. Based on a configuration indicated above, you could provide download protection on all the SYSOP files using a drive and /or subdirectory specification rather than each individual file, and you could also protect the files in the DEFAULT location by simply excluding it's name from the download path specification. You could also have all SYSOP conference uploads go to the SYSOP conference drive\subdirectory location for immediate protection. Since there are an enormous number of combinations available, we will not try and discuss them here. Suffice it to say that you should carefully plan out your configuration BEFORE trying to run PCBoard. If files are not where they belong, your program will either not run, or it will generate errors in doing so. Remember, we will NOT answer any questions about configuration designs or errors generated because of improper configurations. 5 - 2 PCBoard Chapter 5 December 22, 1985 CAUTION: The executable version of the code uses a large amount of code space. It is highly recommended that you shorten your configuration names as much as possible so that the program will not generate a string corrupt error when processing your download 'path' statement discussed later. For example, in the diagram previous, your path statement would have to be something like... C:\PCBOARD;C:\PCBOARD\GEN;C:\PCBOARD\UP; .... etc. By shortening the name of the PCBOARD subdirectory to "PCB", your download 'path' string can be shortened considerably to... C:\PCB;C:\PCB\GEN;C:\PCB\UP; ... etc. saving a considerable amount of machine memory when actually running the program. Please note that this is NOT the path statement used by DOS or set by you in a DOS ".BAT" file. It is the DOWNLOAD 'path' passed to the program through the PCBOARD.DAT configuration file. In order to setup a PCBoard operation, you should have the most current version of PCBOARD.EXE, PCBSETUP.EXE, and all the supporting help, conference, menu, etc. files which are available from numerous PCBoard installations around the US. The files are normally stored in "archive" and "library" format. In order to de-archive these files, you will need a current copy of ARC.EXE (4.50 or later) and LU.EXE. The file libraries you will need are: PCBRDxx.ARC - the main PCBOARD.EXE files with update notes. PCBSETxx.ARC - the main PCBoard setup program. PCBDOCxx.ARC - this documentation. PCBSUPxx.ARC - the supplemental files needed to configure a system. PCBHLPxx.ARC - the 26 HELP files needed for operation 5 - 3 PCBoard Chapter 6 December 22, 1985 C O N F I G U R I N G P C B O A R D -------------------------------------- PCBOARD.DAT is the main configuration data file necessary for proper board operation. The program PCBSETUP.EXE should be used to maintain this file. This file (PCBOARD.DAT) MUST be located on the default drive from which you execute PCBoard. To run the setup program, insure the program PCBSETUP.EXE is in the default location where you intend to load PCBoard. When the setup program loads, it will check for the integrity of the PCBOARD.DAT file. It the file is not found, or it's data items are incomplete, you will be advised of the error and told to insure proper re-configuration before exiting the program. If an error is detected, the code will attempt to "fix" the invalid data item at that time. However, each screen of the program should be reviewed for proper data before exiting the code if an error is detected. There are six main configuration screens available in the program, plus one additional screen for each of the conferences which will be supported. The six main screens are: 1. Sysop Data 2. File Name Data 3. File Locations 4. Modem Data 5. User Levels 6. Miscellaneous Data To enter one of the configuration screens, you should use the [Up] and [Down] cursor control arrows to position the highlighted selection over the desired choice and then press [Return]. Once inside one screen, you can move to the other screens without returning to the main menu by simply pressing either the [PgUp] or [PgDn] keys. To exit from either the program itself, or one of the configuration screens, simply press [Esc]. When exiting from the program itself, you will be asked whether to save the new values to disk. If you response with a [N], the files PCBOARD.DAT and CNAMES will be left unchanged. If the response is affirmative, the program will re-write both the PCBOARD.DAT file and CNAMES file. In the event a subdirectory does not exist for the proper location of the CNAMES file, it will automatically be created by the program before attempting to write the file there. The program will then ask if you wish to check your program path configuration. If you respond with a [Y], the program will run through ALL path specifications defined - including conference paths - to verify their presence. As this is done, any subdirectories which do not exist will automatically be created by the program. Also, since the program checks ALL paths, you may see some "double" checking of a previously checked path. This is not a program bug. It is simply checking every path it needs to before continuing. In the case of inclusion of either the '\GEN', '\MAIN' or '\HELP' locations in the download path, you will see the path checked twice - once for the initial location and again during the download path check - where all entries in the download path are verified as being present. Likewise, if you have some conference file locations which are the same as some of the other drive locations specified, you will see these "double" checked as well. Note: When using the program PCBSETUP.EXE to create and maintain the 6 - 1 PCBoard Chapter 6 December 22, 1985 PCBOARD.DAT file, you are asked to respond with "Y" or "N" to answers which are actually stored in the file as "-1" and "0". Please note that the items discussed on the following pages which reference an entry of "Y" or "N" may actually be stored as "-1" and "0" in the PCBOARD.DAT file. The editing commands available within PCBSETUP include: [Home] Go to beginning of current field [End] Go to end of current field [Right-Arrow] Move right in current field [Left-Arrow] Move left in current field [Up-Arrow] Move up to previous field [Down-Arrow] Move down to next field [PgDn] Move to next data page [PgUp] Move to previous data page [Ctrl-End] Delete from cursor to end of field [Delete] Delete character under cursor [Backspace] Delete character to left of cursor [Insert] Insert characters starting at cursor position The PCBSETUP program will adjust it's main menu accordingly based on the number of conferences you specify. *** NOTE *** To add or delete conference entries, simply change the number of conferences in the MISCELLANEOUS screen. This will automatically adjust the main menu and will allow you to create the necessary conference paths on exiting the program. Note that it will not remove previous subdirectories which are present but are no longer needed. Also note that the program will attempt to edit as much of your data as possible. If the program detects an invalid entry, it will BEEP at you and change the value back to the original one. Double check the valid entries by referring to this manual, or use the prompts provided next to the display for assistance. Following are discussions of the data items in each of the PCBSETUP screens and what to enter in each. 6 - 2 PCBoard Chapter 6 December 22, 1985 Screen 1 - Sysop Data --------------------- Entry # 1 - Program Display Name of the Sysop (YourName) ------------------------------------------------------------------------ This is the name of the sysop which is displayed at several points during normal program operation. The name must be one word only. You should enter your first name as the default - capitalizing the first letter for better appearance during program display. Entry # 2 - Local Password/Remote 'First Name' (PASSWORD1) ------------------------------------------------------------------------ This is the password needed to logon locally as a sysop. It is also the 'first name' to be entered when logging on from a remote location. This password is of course definable by the sysop. DO NOT set this and the next entry to your actual name. If you do, anyone who logs on with your name will immediately be considered the sysop!! Entry # 3 - Remote 'Last Name' Password (PASSWORD2) ------------------------------------------------------------------------ This is the 'last name' password which should be entered when logging on from a remote location. CAUTION: Guard the above two items well and change them frequently to prevent un-authorized access into your system!! Entries # 4-13 - Sysop Security Levels (Various) ------------------------------------------------------------------------ These are the 10 sysop menu security levels for the 'sysop' only functions available in the program. These function levels should all be between 100 and 110. When a sysop exits to DOS and returns, he receives a level of 110. Callers who are granted temporary sysop privileges are given a temporary security level of 100. Users must have a security level of 105 or greater to be able to read/kill/unprotect/protect ALL messages. If their security level is less than 105, they can only read and kill messages to themselves. NOTE: The board is semi-hardcoded for all sysop functions to be in the range of 100-110. A level of 110 MUST be assigned for sysop function number 9 - Exit to DOS from remote. A sysop signing on using the two sysop passwords is automatically assigned a security level of 110. Sysop function menus are not displayed for user's whose security level is less than 100. Users who have a security level of 100 or above can do most of the sysop functions for which they have the proper security level. It is highly recommended that you DO NOT assign sysop function 7 (maintain user data base) to your associate sysops unless you trust them completely!! The reason being that they have the ability (if function 7 is active) to read and scan the entire user file for passwords, etc! This board was designed so that basically only one person should function as the actual sysop. 6 - 3 PCBoard Chapter 6 December 22, 1985 Screen 2 - File Name Data ------------------------- Entry # 1 - Name of Messages File (MSGS) ------------------------------------------------------------------------ This is the name of the main board's message file. It must be no longer than 8 letters and must not contain a filename extension - since the filename of <filename>+.BAK is used by the program when the messages are packed. When messages are packed, the current backup message file is deleted, the active message file is renamed to now be the backup file, and the new message base is built by reading in the records from the now .BAK file - dropping killed messages in the process. This file is automatically created by the program if it does not exist. The file must be kept in the 'MAIN' subdirectory location as indicated below. If you are converting an RBBS message file to PCBoard, you MUST repack the file immediately after the conversion. Failure to perform the repack may result in erroneous program operation when reading or entering messages. If you are also converting conference message files, it is recommended that you temporarily rename them to the main message base for repacking, followed by renaming them back to the appropriate conference name. This name is also used when creating the text file outputted by the code during use of the [Alt-F] (file out) function. When the [Alt-F] key is active in the code, the file is written to a disk file called <message base name>+".TXT". More information concerning text output is available later in the documentation. Entry # 2 - Name of the Caller's File (CALLERS) ------------------------------------------------------------------------ This is the name of the file which stores all caller log information. This file is automatically created by the program if it does not exist. The file is stored in the 'MAIN' subdirectory. The file information is written in blocks and can not be 'typed' to the screen. However, the contents of the file can be outputted to a local printer while the sysop is logged onto the system in local mode and displayed to the local screen as well. Entry # 3 - Name of the Comment's File (COMMENTS) ------------------------------------------------------------------------ This is the name of the file containing all comments left for the sysop. The file is automatically created by the program if it does not exist. The file must be stored in the 'MAIN' subdirectory. The file can be 'typed' to the screen or printer if desired. The program also provides the sysop with the ability to print out this file from either his local station or from remote to his board's local printer. The file can then be deleted. Entry # 4 - Name of Welcome File (WELCOME) ------------------------------------------------------------------------ This is the name of the 'Welcome' file displayed to all users as they logon to the system. There must also be a color version available which has the letter "G" appended to it. In other words, if you call the file WELCOME, 6 - 4 PCBoard Chapter 6 December 22, 1985 there must also be a graphics version on the board called WELCOMEG for the color graphics callers. These files must be located in the '\GEN' board subdirectory location. Entry # 5 - Name of the Newuser File (NEWUSER) ------------------------------------------------------------------------ This is the name of the file displayed to all new users as they logon to the system. There should NOT be a color version available. This file must be located in the '\GEN' board subdirectory. CAUTION: If this file is too long, the caller will not have enough time to read the file and complete their registration information before the initial 5 minute program time limit has expired. Keep the file short and reference a bulletin for them to read if you need a longer file for them to review for registration information. This board's code was designed for quick running - not for verbose sysop text files! Entry # 6 - Name of the User's Data Base File (USERS) ------------------------------------------------------------------------ This is the name of the file used to store all user data base information. The file will automatically be created if none exists. The filename must be 8 characters or less with no extension. The file must be placed in the '\MAIN' subdirectory. Entry # 7 - Name of the Conference Data File (CNAMES) ------------------------------------------------------------------------ This is the name of the file used to store all conference information. It must be created and maintained using a text editor. The file must be kept in the '\MAIN' subdirectory on the board. Entry # 8 - Name of the Download Security File (FSEC) ------------------------------------------------------------------------ This is the name of the file used to store all of the download file security information. It must be maintained using a text editor and it must be kept in the '\MAIN' subdirectory on the board. Entry # 9 - Name of the Logon User Time Allowance File (PWRD) ------------------------------------------------------------------------ This is the name of the file used to store all of the logon password and time allocation information. It must be maintained using a text editor and stored in the '\MAIN' subdirectory on the board. Please note that you MUST have a corresponding entry in this file for each of the assigned security levels you give to your callers. If you do not have a matching security level here - which is exactly the same as one of your callers - they will receive a default of only 10 minutes on your system. Entry # 10 - Name of the Undesirable Caller's Names (TCAN) ------------------------------------------------------------------------ This is the name of the file used to store all of the names which will automatically be denied access to the system. If a match is found on any 6 - 5 PCBoard Chapter 6 December 22, 1985 name in this file against either the caller's first or last names, they will be denied access to the system. This file must also be built and maintained using a text editor and must be located in the '\MAIN' subdirectory. Callers who log onto your system and use one of the names in the TCAN file will have their logon entry written to the caller's log for review. To build the file, simply enter the name you wish to restrict in captial letters on line line of the file. For example, you file may include such items as: ----------------------- MR. HACKER HAPPY THE WAR ----------------------- If any caller logged onto your system who used any of the above entries as either their first or last names, they would immdediately be denied access to your board. Entry # 11 - Name of Batch File Called Exiting Remote (REMOTE) ------------------------------------------------------------------------ This is the name of the batch file called up when the sysop exits to DOS from a remote location. The filename must be 8 letters or less and must NOT contain an extension. The actual file should be placed in the default drive/subdirectory location of the system from which PCBoard is initially run as <filename>+.SYS. The program will automatically rename the file to REMOTE.BAT just before the sysop actually exits to DOS. The file REMOTE.SYS included provides a sample of the file. The board itself must be called by another file called BOARD.BAT - so the two batch files can interact with each other. If you do not understand the use of .BAT files in remote operation, set the # 9 sysop function security level to 120 to prevent anyone from using the function - including yourself. 6 - 6 PCBoard Chapter 6 December 22, 1985 Screen 3 - File Location Data ----------------------------- Entry # 1 - Main Board Upload Location (C:\PCB\UP) ------------------------------------------------------------------------ This is the drive\subdirectory location where all files uploaded in the main section of the board will be placed. It can be separate from all other directory locations for security purposes and does not need to have the upload directory listing on the drive. The drive designation is mandatory. Failure to specify a drive location may result in a program error or erroneous displays. Entry # 2 - General Drive/Subdirectory Location (C:\PCB\GEN) ------------------------------------------------------------------------ This is the drive and subdirectory location where the following files MUST be located: BLT & BLTG (Main Board Bulletin Menus - Hardcoded) BLTxx (Actual Bulletins for Main Board - Hardcoded) DIR & DIRG (Main Board File Directory Menus - Hardcoded) DIRxx (Main Board Directory Lists - Hardcoded) WELCOME & WELCOMEG (Welcome Files - mono and color - Definable) NEWUSER (Newuser Instruction File - Definable) NEWS & NEWSG (General Board 'News' files - Hardcoded) CNFN & CNFNG (Conference Menu File - Hardcoded) BRDM & BRDMG (User's Main Menu - Hardcoded) BRDS & BRDSG (Sysop's Main Menu - Hardcoded) The drive designation is optional. Entry # 3 - Main Drive/Subdirectory Location (C:\PCB\MAIN) ------------------------------------------------------------------------ This is the drive and subdirectory location where the following files MUST be located: MSGS (Main Board Message File - Definable) CALLERS (Caller's File - Definable) COMMENTS (Comment's File - Definable) FSEC (Download File Security File - Definable) PWRD (Logon Password/Time Allowed File - Definable) CNAMES (Conference Information File - Definable) ASK.DAT (Main Board Questionnaire Questions) NEWASK.DAT (Private Board's Registration Questions) NEWREG.DAT (Registration data saved from closed board) DOWNLOAD.TXT (Download file information for call analyzer programs) This drive\subdirectory location can be eliminated from the download path to prevent anyone from downloading these files under any circumstances. The drive designation is optional. 6 - 7 PCBoard Chapter 6 December 22, 1985 Entry # 4 - Help Drive/Subdirectory Location (C:\PCB\HELP) ------------------------------------------------------------------------ This is the drive and subdirectory location where the 26 help files MUST be located. Files are hardcoded to the filename of HLP+ the letters A-Z corresponding to the 26 possible selections available. For example, the file HLPB would be the file which provides help for reading bulletins. The drive designation is optional. Entry # 5 - Download Path String (\PCB;\PCB\DL1 ... etc ------------------------------------------------------------------------ This is the path which MUST be specified to allow downloads from any and all disk drive locations - including the default drive\subdirectory. If a drive\subdirectory is not included in this path, files in it are NOT available for downloading. The drive designation is optional. CAUTION: The maximum number of drives/subdirectories CAN NOT exceed 50!! All entries must be made on one line - separated by a semi-colon as is normally done with conventional path specifications. All entries in this line must match exactly with security entries made in the file security file (FSEC)!! NOTE: Setting 'path=' in your autoexec.bat file will have NO effect on PCBoard program operation. Only the 'path' string passed to the program through the PCBoard.DAT file will be used by the program to find downloadable board files. 6 - 8 PCBoard Chapter 6 December 22, 1985 Screen 4 - Modem Data --------------------- Entry # 1 - Modem Reset String (ATZ) ------------------------------------------------------------------------ This is the modem command needed to reset your modem just before re-opening it to receive calls. Entry # 2 - Modem Initial Open String (ATS2=255S10=8S7=21M0X1) ------------------------------------------------------------------------ This is the modem command needed to initially set the modem to receive calls. Entry # 3 - Modem Off-Hook String (ATS0=0H1M0) ------------------------------------------------------------------------ This is the modem command needed to place the modem 'Off-Hook' with the line in a busy mode. The above 3 modem commands are compatible with a Hayes 1200 baud, Courier 2400 baud, Multi-Tech 2400 baud modem and others. Some modems are NOT compatible with the above settings and erroneous program operation may occur. You must also have pin 22 active in order for the program to properly answer and hang-up the phone. If pin 22 is not active, the program may not run. A U.S. Robotics PASSWORD and QUBIE modems are two that WILL NOT work with this code. NOTE: If you are using a 2400 baud modem, you must specify 2400 baud as the opening speed of your modem. See additional information concerning modem switch configurations in Chapter 4 - Modem Switch Settings. Entry # 4 - Communication's Port Being Used (COM1:) (COM1: or COM2:) ------------------------------------------------------------------------ This is the communication's port which the board is using. It can only be COM1: or COM2: Be sure and include the colon as part of the entry. Entry # 5 - Baud Rate to Open Modem at (2400) (300,1200,2400) ------------------------------------------------------------------------ This is the speed at which the communication's port is to be opened. Sysops with 2400 baud modems should enter 2400. All others should enter 1200 or 300. The 2400 baud entry is to prevent modem lock-up during modem reset when a caller hits the system. Entry # 6 - Allow 300 Baud Callers Access (Y) (Y or N) ------------------------------------------------------------------------ This flag determines whether the board allows 300 baud callers access into the system. If the flag is set to "N", all 300 baud callers are DENIED access. If the flag is set to "Y", they are allowed into the system. An appropriate message is displayed if you lock-out 300 baud callers. NOTE: This software does NOT support callers at E,7,1 data settings! Only 6 - 9 PCBoard Chapter 6 December 22, 1985 callers at N,8,1 are accepted. If a caller calls at E,7,1 they will get garbage on their screen. Entry # 7 - 300 Baud Caller Start Time Access (00:00) (Definable) ------------------------------------------------------------------------ If you set the previous entry at "Y" (allow 300 baud callers), you can set a time period to allow them access to your system if desired. This entry is the start time of their access in hh:mm format. For instance, if you only want to allow 300 baud callers access from 11:00pm to 6:00am, you would enter 23:00 in this position. (Military time) Note: The program properly compensates for the midnight time change. Entry # 8 - 300 Baud Caller End Time Access (00:00) (Definable) ------------------------------------------------------------------------ This entry is the end time of 300 baud caller access in hh:mm format in military time. In the above example, your entry here would be 06:00. If you wish to allow 300 baud callers at all times, the previous entry should be 00:00 and this one 24:00. If a caller logs on outside of the allowable 300 baud access time(s), they will be shown a message indicating the hours 300 baud is supported. Note: The program properly compensates for the midnight time change. 6 - 10 PCBoard Chapter 6 December 22, 1985 Screen 5 - User Levels ---------------------- Entries # 1-26 - User Security Levels (Various) ------------------------------------------------------------------------ These are the 26 main menu security levels for the various menu selections available to the caller. These security levels should correspond to your needs based on the values you specify for new 'registered' users, new users who refuse to register, and your registered users and conference users. Entry # 27 - Level Assigned New Users Who Register (40) ------------------------------------------------------------------------ This is the security level assigned new users who complete the board's registration information - which asks for their name, city and state, password desired, business/data phone number, voice/home phone number, and their default transfer protocol desired. If the board is flagged as a 'private' board, a user is granted this security level upon completing the registration information asked from the NEWASK.DAT file. If the board is private, all new user information is written to a special Ascii text file called NEWREG.DAT which is automatically created in the '\MAIN' location for protection purposes. If the board is public, new user information is written to the main user's file. Entry # 28 - Level Given New Users Who Refuse To Register (30) ------------------------------------------------------------------------ This is the security level assigned new users who refuse to complete the requested registration information. If you specify 0 here, all callers who refuse to register will be immediately logged off. 6 - 11 PCBoard Chapter 6 December 22, 1985 Screen 6 - Miscellaneous ------------------------ Entry # 1 - Number of Main Board Bulletins (6) (1-99) ------------------------------------------------------------------------ This is the number of active bulletins in the main section of the board. The number can not be greater than 99. You can specify a number of zero if desired. This number should be set equal to the number of active main board bulletins you will be posting. Entry # 2 - Number of Active Conferences (2) (1-9) ------------------------------------------------------------------------ This is the number of conferences active. The maximum number of conferences allowed is nine - since all conference information is stored as a single digit ascii character between 1 and 9. However, it is STRONGLY recommended that you do not try and configure your system with more than 5 total conferences. The reasons for this are that you can experience program errors if you do and your are probably not properly serving your caller's needs if you try and support more than 5 total conferences. CAUTION: If you change the order of the conference listings in the CNAMES file, the user's file many then contain erroneous information. For example, if JOHN DOE is registered in conference # 2 - GAMES - and you insert a new conference between 1 and 2 in CNAMES - moving games up to conference # 3 - JOHN DOE will still be registered in conference # 2 - which is now the new conference. DO NOT change the order of the conferences unless absolutely necessary since you will have to manually go through the entire user data base recoding all of the user's conference registration information! Note: You must change the number of conferences here in order for the PCBSETUP program to allow you to configure that conference. The number of conferences entered here determines the number of Conference's which will appear in the main menu. Entry # 3 - Maximum # of Main Board File Directories (10) (1-99) ------------------------------------------------------------------------ This is the number of active main board file directory listings. All file directories are hardcoded to the name DIRxx where the xx is the actual directory number. Directories must be numbered sequentially from one (1) up to the number specified - in increments of one (1). Conference directories are numbered from this number plus one up to the number of conference directories as specified in the CNAMES file. Conference directories have the first letter of the conference name prefacing their name. For example, if you have a sysop's conference which has an additional 6 file directories, they would be called SDIR11 through SDIR16 - with the main board directory listings named DIR1 through DIR10. The maximum number of main and conference file directory listings can not exceed 99 for any single combination of the two. 6 - 12 PCBoard Chapter 6 December 22, 1985 Entry # 4 - Daily Time Limit Flag (Y) (Y or N) ------------------------------------------------------------------------ This flag when set to "Y" means callers are limited to a maximum amount of time per day based on their security level. If the value is set to "N" callers can call as many times as they like - each time getting a full time limit. Entry # 5 - Make Main Board Upload Directory Private (N) (Y or N) ------------------------------------------------------------------------ This flag sets whether callers can view recent uploads to the board. If the flag is set to "Y", all upload information automatically goes to a file called PRIVATE (Hardcoded by the program) - which should be protected from downloading by inclusion in the FSEC file. If this flag is set to "N", all upload information goes to the highest number general board file directory which is by default the upload directory. Users who begin their upload description with a "/" also have their information placed in the PRIVATE file rather than the regular upload directory. Upload directories which are not present on the appropriate drive are automatically created by the program to prevent loss of upload information. If you make your main board upload directory private, you can call the highest numerical directory on your system something other than the 'upload' directory - since all upload information is placed in a private file accessible only by the sysop. Entry # 6 - Deny User's Complete Data Base Update (N) (Y or N) ------------------------------------------------------------------------ This flag determines whether a user can update just their password, or their complete data base information - including their city and state, both phone numbers, and transfer protocol plus password information. Note: This flag is carried throughout the entire program. (i.e. Conference members are treated just like regular board callers.) By setting the flag to "Y", users are allowed to update all their information. If set to "N", they can only change their password. If the board is private, you should set the security level for password and/or data base changes to a level above that of a new user. If you forget, the program will still not allow a non-registered user to try and actually update the data base. Entry # 7 - Closed Board Flag (N) (Y or N) ------------------------------------------------------------------------ This flag determines whether a user can leave any registration information in the main data base. If this flag is set to "Y", all new user registration information is written to a file called NEWREG.DAT which is automatically created in the '\MAIN' drive location. The information is stored in ascii text and can be viewed or edited easily. The sysop then has the choice of taking the names he wants from this file and entering their information into the main program data base. No new callers are added to the user's file unless the sysop puts them in himself. If this flag is set to "Y" (closed board), AND the file NEWASK.DAT is missing, then no new users will be allowed into the system - even for a few minutes. If you want a new caller to be at least able to browse through your system, the NEWASK.DAT file must be present. If you wish them to browse without having them enter any data, simply place a [Ctrl-Z] as the 6 - 13 PCBoard Chapter 6 December 22, 1985 only entry in NEWASK.DAT. In this case, just a date and time stamp will be written to the file as each new caller is logged into the system CAUTION: There is no upper limit on the size to which the user's file can grow!! Pack and delete old users on a regular basis. Likewise, there is no upper size limit to the NEWREG.DAT file. Purify this file on a regular basis. The questions which are asked the new caller who agrees to register on a closed board MUST be stored in a file called NEWASK.DAT - which must be located in the '\MAIN' drive\subdirectory location. The file should consist of one line entries which are the questions asked the user. This file should have no less than 1 question. It does not have a upper limit to the number of questions which can be present. An example of the file appears below: ------------------------------------------------------------------------ Full Name (F&L) Mailing Address City/State/Zip Bus/Data Phone Home/Voice Phone Password Desired Special Comment ------------------------------------------------------------------------ As the file is processed (similar to the questionnaire file), the answers along with the individual questions are written to the NEWREG.DAT file in the '\MAIN' drive\sub location. This file can then be 'typed' to the printer or edited with a text editor if desired. Callers are required to answer EVERY question that is presented to them from the NEWASK.DAT file. They are not allowed to skip a question by just pressing their carriage return. However, no edits of the data entered are performed. In other words - they can enter junk into the file. Entry # 8 - Run Board in Non-Graphics Mode (N) (Y or N) ------------------------------------------------------------------------ This flag can be set to "Y" to indicate that NO graphics support is available. When this flag is set to "Y" (no graphics), all callers are denied a mode change to graphics. Also, all text output to the sysop's machine is done through a PRINT statement rather than the ANSI.SYS driver built into the code. This feature can be used by sysops running the code on less than desirable screen displays where the internal program color generation does not fare well. As a sidenote, your can improve the appearance of your screens in graphics mode (bad display sysops) by initializing the DOS mode command as BW80 prior to running the code. Also, this feature works well when running the code under some multi-tasking programs which do not properly support the ANSI.SYS driver. The code has been tested using Multi-Job with the graphics flag on and it's performance is fine. 6 - 14 PCBoard Chapter 6 December 22, 1985 Entry # 9 - Automatic Conference Assignment (000) (Definable) ------------------------------------------------------------------------ This is the string which you can define which will be written to the user data base whenever a new caller is logged into the file. The string can contain up to three conference numbers which you wish to make public. If you do not desire that callers be automatically granted access to your conferences, the string should be set to "000". If for instance, you had 4 conferences - of which 1, 2 and 3 were public, you could set the string to "123" - which would immediately allow all new callers who get registered into the data base access to these three conferences. Entry # 10 - Size Limit of Comments File (15000) (Definable) ------------------------------------------------------------------------ This entry allows you to determine the maximum size (in bytes) you wish your comments file to grow to before not allowing any more comments. It's purpose is to prevent a user from filling up your drive with comments. If you do want your callers to be able to leave any comments, set this value to 0. Entry # 11 - Name of Your Board (Salt Air Premium Bulletin Board) ------------------------------------------------------------------------- This is the name of your bulletin board. It will be displayed to the caller when they initially log onto your system. The version number of the software will also be displayed at this time along with your board's name. Entry # 12 - Event Timer Active (N) (Y or N) ------------------------------------------------------------------------- This flag when set to "Y", means that you have an event which you wish to run at a given time using the interactive batch file EVENT.SYS - which must be located on your default drive. If this flag is to true, the board will begin adjusting all caller's times before the event time to prevent their being logged on at the time the event is scheduled to run. This allows the sysop to specify a time of day at which the board will exit to DOS to execute another function. This capability was provided for several reasons - including the ability of the code to function in a 'mail node' system, and also to allow the sysop to perform automatic streamer tape backups, etc. The event timer can also be used to shut your board down at a given time for maintenance, etc. The operation of the event timer is somewhat tricky and must not be used unless you completely understand the use of interactive batch files. If you do not know how to create and maintain batch files which have logic built into them, do NOT attempt to use this function. In the miscellaneous screen of the code, you will see two additional questions: 1) Timed Event Active and 2) Event Run Time. If you set timed event active by entering a "Y", several things will occur during PCBoard operation. First, every time a caller logs onto your system, the code will look to see how much time remains before the event is to occur. (The code will properly adjust for the midnight time change problem) It will then subtract 5 minutes from that time and compare it to the caller's allowed time. This 5 minute subtraction of time is to allow for a 5 minute 'buffer' before the actual event. If the net time before the event is less than the caller's allowed time, the caller's time will be adjusted downward to reflect the actual time available before the event begins. They will also be advised that their time for that call has been adjusted, and why, each time the main 6 - 15 PCBoard Chapter 6 December 22, 1985 menu command line is displayed. For example, if a caller were to call your system 1/2 hour before an event were to occur and their normal allowed time was 1 hour, they would be shown they only have 25 minutes available (30 minutes before the event minus the 5 minute buffer.) Also, a message would appear indicating their time had been adjusted. If they called later in the day, they would receive their full 60 minutes minus the actual time used during the previous calls that day. Five minutes before the event is scheduled to begin, ALL callers will be denied access to the system. If they log on, they will be displayed a message that the board is not available. This procedure continues up until 15 seconds before the event is to begin. If a caller hits the system during this time, the board will display the message to the caller, log them off, and will then proceed with the event. If no callers are hitting the system during this 'buffer' time, the code will run the event at the proper time. NOTE: NO uploads are allowed during the time preceding an event IF the caller's time has been adjusted! This is to prevent a caller from getting on-line and starting a big upload which would carry it past the scheduled event time. Finally, as the event is called by the program, the board looks for a file called "EVENT.SYS" on the default drive. If it finds it, it will rename the file to "EVENT.BAT" and exit to DOS. If the file is not found, the program will simply recycle. The file "EVENT.SYS" should be the batch file used to call up another program or function which is to be performed at the scheduled time. The logic of allowing this additional batch file to function properly in conjunction with BOARD.BAT is shown in the example below... -------------------------------------- BOARD.BAT (file example) -------------------------------------- c: cd\pcb if exist remote.bat rename remote.bat remote.sys if exist event.bat rename event.bat event.sys if exist endpcb del endpcb pcboard if exist remote.bat remote if exist event.bat event if exist endpcb goto end board :end cls^Z -------------------------------------- What occurs now is that when PCBoard exits to DOS, it not only looks for the presence of the REMOTE.BAT file, but also the EVENT.BAT file which was created by renaming a file called EVENT.SYS from inside the code just before exiting. If the file EVENT.BAT is found, it is run. That file should then contain the instructions of the actual remote event, finishing with a statement which recalls BOARD.BAT. An example of an EVENT.SYS file follows... ---------------------------------------------------- 6 - 16 PCBoard Chapter 6 December 22, 1985 EVENT.SYS (sample file) ---------------------------------------------------- copy d:\up a:\ board ---------------------------------------------------- The above example is very simplistic. It would simply copy every file from your upload directory to a disk on drive "A" and then re-run BOARD.BAT- bringing the board back up on-line. The event sys can be as simple or complicated as desired. Again, if you do not understand the logic of the above example and how to interface another batch file to work with BOARD.BAT, DO NOT turn the event timer on! A properly configured system will attempt to recycle the board if there is a problem. However, it can not trap for every error which can be made in such an environment and therefore may cause your system to crash. This feature was placed in the code for the more advanced sysops who desired such a function. It is not intended for the novice sysop! Additionally, you can have the EVENT.BAT file overlay other files on top of the current PCBOARD.DAT file which can be used to call other subsequent events at other times of the day. In other words, you can schedule as many timed events as desired using this one simple feature. Entry # 13 - Event Time (00:00) (Definable) ------------------------------------------------------------------------- This entry is the time of day the above event is to occur. The time should be entered in military format in hours and minutes only. If the above flag is set to "N", this time is disregarded by the program. Entry # 14 - Max # of Message Lines (17) (1-60) ------------------------------------------------------------------------- This entry allows you to specify the maximum number of text lines which are allowed when someone is entering either a message or a comment. The maximum number allowed is sixty. The program will automatically provide intelligent page pauses for your callers - depending on the maximum size you decide each message can be. Entry # 15 - Default Color Intensity (00) (00 or 01) ------------------------------------------------------------------------- This is the ANSI code that can be set to determine whether text which is entered either at the local keyboard or by the caller from remote will appear in normal or high intensity color. If the string is set to "00", the color will be normal intensity. If set to "01", the ANSI driver will make all caller entries and local keyboard entries appear in high intensity color when in graphics mode. Entry # 16 - Default Foreground Color (37) (31-37) ------------------------------------------------------------------------- This entry should contain the ANSI escape code for the default color you wish the local keyboard input and the caller's input to be displayed in on the screen. The valid color codes are: 6 - 17 PCBoard Chapter 6 December 22, 1985 31 - Red 32 - Green 33 - Yellow (Brown) 34 - Blue 35 - Purple 36 - Light Blue (Cyan) 37 - White These are codes which are used by the ANSI driver. If the caller has requested graphics mode, all of their entries, and some of the information displayed to them by the board, will appear on their screen and the local screen in this color. If they have not selected graphics mode, this color will still appear on the local screen. These colors can be set in combination with the intensity value above to achieve your own desired color combination. 6 - 18 PCBoard Chapter 7 December 22, 1985 C O N F I G U R I N G C O N F E R E N C E S ---------------------------------------------- CNAMES is the default file used to store all conference information. The file must reside in the 'MAIN' subdirectory location and should be maintained using the program PCBSETUP. In order to add or delete a conference using the program - simply enter the number of active conferences in the "Miscellaneous" screen of the PCBSETUP program. This will automatically adjust the program to read and write the proper number of conference entries to the CNAMES file. The program will also automatically create all subdirectories - including conference subdirectories - on exiting the program. An example of the actual file is shown below: ---------------------------------------------------------------------- Sysops,#,3,4,0,Y,C:\PCB\SYSOPS,C:\PCB\SYSOPS,10,0 Games,$,2,2,-1,N,C:\PCB\GAMES,C:\PCB\GAMES,0,30 ---------------------------------------------------------------------- Each conference must have a single line of data in the file for it. In the example above, the board is running two conferences - one called 'Sysops' and the other 'Games'. The items needed for each conference are as follows. Entry # 1 - Name of the Conference (Sysops) ------------------------------------------------------------------------ This is the name of the conference as it will appear at several points throughout the program. It is recommended that the name be entered with a capital first letter and the rest lower case to enhance program display. CAUTION: All conference names should start with a different letter if possible to prevent conflicts if several conferences occupy the same drive location. This is also the name of the message file inside of the conference! The name must be one word with no extension. (8 letters max) In other words, the conference message file would be called SYSOPS in the example shown. The program uses the first letter of the conference name to dynamically build several other filenames - including the conference bulletin files and directory files. In other words, when creating your file directory listings for a given conference, they should begin with the first letter of the conference, include the "DIR" default as the middle part of their name, followed by their actual directory number - which is the maximum number of general board directories + it's number. For example, the sysop's conference example shown above would have 4 additional file directories - SDIR11 to SDIR14 - with SDIR14 being the upload directory. The Games conference would only have two additional directories - GDIR11 and GDIR12 - with GDIR12 being the upload directory. Entry # 2 - Conference File Security Character (#) (!#$%&'-() allowed) ------------------------------------------------------------------------ This is the Ascii character which is a legal filename character (see your basic or DOS manual) which is below Ascii 48 that is used to protect all conference files from downloading except within the actual conference. If a 7 - 1 PCBoard Chapter 7 December 22, 1985 caller specifies conference security on an upload, the filename the user enters is automatically changed so that the last letter of the filename becomes the character specified. For example, in the listing above, sysop conference files are protected with the # sign. A file called TEST.COM which a user uploaded to the conference and desired to place conference security on would be renamed to TEST.CO# before actually beginning the upload. The user does not have to do any renaming prior to uploading. The conference will automatically handle the renaming function. Once a file is modified with the character shown, it can only be downloaded while inside of the conference. This means that you can protect a large number of files on your system by simply renaming them and placing them inside a conference. Even the sysop can not download the file outside of the conference! If you do NOT wish to actually perform a file re-name function - but still want your user's to have the option of where the upload description is placed, simply specify the character as a null. (i.e. Sysops,,30,40 ...etc) By not specifying a character, the filename will not be altered, but it will physically be placed in the conference upload drive\subdirectory, and it's description will appear in the conference upload listing. In general, callers specify at the time of an upload whether or not they want to place conference security on the file they are sending to the board. If they say 'Yes', the file description is placed in the conference upload directory listing and the file is placed in the conference upload subdirectory. If they say 'No', the file description is placed in the general board upload directory and the file is physically placed in the main board's upload directory. This is to allow for additional file security location(s) and helps in sysop house-cleaning chores. If a character is specified here, all of the above functions occur - plus the file is renamed in the process - restricting downloading to callers inside the conference only. Entry # 3 - Number of Conference Bulletins (3) (1-99) ------------------------------------------------------------------------ This is the number of active conference bulletins. (Similar to the general board information.) Conference bulletins are named and numbered the same as main board bulletins - with the exception that the first letter of the conference name must precede the BLTxx. In other words, the sysop's conference example would have SBLT1, SBLT2 and SBLT3 as it's actual conference bulletins. Additionally, you need two more bulletin menu listings for the conference - SBLT and SBLTG - which contain a description of the bulletins available in that conference. All of these files must be located inside the conference subdirectory specified below. Entry # 4 - Number of Additional File Directory Listings (4) ------------------------------------------------------------------------ This is the number of additional file directories used to store conference file information. The actual directories are named the same as the main board files with the exception of adding the first letter of the name of the conference to the file name. (i.e. SDIR11, etc.) The actual directories should be numbered starting at 1+the number of main board directories up the number specified. In the example(s) listed so far where the main board had ten (10) directories, all conference directories would begin with the number 11 - up to the maximum number of additional files - in this case 4 or SDIR14. The Games conference would only have two additional directories- 7 - 2 PCBoard Chapter 7 December 22, 1985 (GDIR11 and GDIR12). You must also have a new file directory listing menu called 'DIR' which also has the first letter of the conference prefaced to it. In the case of the sysop's conference, you would need two files - SDIR and SDIRG (color version) which would show the caller the 10 regular board file listings plus the additional 4 conference listings. EACH conference must have it's own xDIR and xDIRG files! All conference file directory listing(s) MUST be located in the conference subdirectory indicated below. Entry # 5 - Conference Private Upload Flag (N) (Y or N) ------------------------------------------------------------------------ This flag determines whether uploads to the conference will be placed in the sysop's private upload directory or in the conference upload directory. If the caller specifies that a file should have conference security and the conference flag is set to private - "Y", the upload description will be placed in the sysop's private upload directory for that conference (which is a DIFFERENT private file than that used by the general board!) The name of this private file is the word "PRIVATE"+the first letter of the conference name. For example, the sysop's conference private upload directory would be called PRIVATES. The game's would be PRIVATEG. You can have several combinations of main board/conference 'private' flags to suit your needs. For instance, you can have a private main board upload directory and a 'public' conference upload directory - or visa versa. If the user places a "/" in the file description entry - it too will be placed in the conference private file (if they have specified conference security!). If they do not specify conference security, the description will be placed in the main board's upload directory (private or public) as necessary. The bottom line is this. The file description can be placed in any one of FOUR locations depending on how you have your main board and conference 'private' flags set - and/or whether the caller uses the "/" as the first letter of their upload description! Again, if an upload directory does not exist - it will automatically be created by the program so that no upload information is lost!! To help out with this somewhat confusing structure, the program has been designed to visually show the user where his file description is being placed and it's display status (screened or public). Hopefully this will help eliminate some questions from your user's (or you) on where their file went!! Entry # 6 - Auto-Rejoin Conference on Next Call (Y) (Y or N) ------------------------------------------------------------------------ This flag determines whether a caller will automatically be placed back inside the conference they have hung-up in. If the user hangs up from the main section of the board - they will NOT be returned to a conference - even though the flag is set at "Y" for yes. Only if the flag is set to "Y" AND the caller hangs up inside the conference will they be returned automatically to it the next time they call. If the flag is set to "N" for no, the caller will not be automatically returned to the conference on their next call. If the flag is set to "Y", the user will be given the opportunity of scanning the main board's message 7 - 3 PCBoard Chapter 7 December 22, 1985 base before actually entering the conference - so that they will not miss any general board mail addressed to them. Entry # 7 - Conference File Upload Directory (C:\PCB\SYSOPS) ------------------------------------------------------------------------ This is the drive\subdirectory where all files which are specified as having conference security are placed. The drive designation is optional. Uploads on which the caller does NOT place conference security go to the main board's upload location - not the conference's!! Entry # 8 - Conference Drive/Subdir. Location (C:\PCB\SYSOPS) ------------------------------------------------------------------------ This is the physical drive location of all conference files including the conference message file which has the same name as the conference - i.e. SYSOPS in the case of the sysop's conference, and also the files below: (Sysop's conference used for example only!) SYSOPS (Conference message file) SDIR & SDIRG (Directory Listings) SBLT & SBLTG (Bulletin Listings) SDIRxx - SDIRxx (Actual conference file directories) SBLTxx - SBLTxx (Conference bulletins) PRIVATES (Conference 'private' directory) The drive designation is optional. Entry # 9 - Additional Conference Security Level (10) (Definable) ------------------------------------------------------------------------ This is the amount of additional security you wish to give users when they join a conference. If you wish to award them none - enter a zero (0). This additional security is ONLY effective while they are inside the conference. Once they leave - or jump to another conference - they loose that respective conference's additional security level. NOTE: Callers can go from conference to conference without abandoning the conference they are in. For example, a caller who is registered in both conferences 1 and 2 can go back and forth at will by entering the stacked command "J 1", "J 2" (J;1, J;2) etc. If a caller is registered in more than one conference, his total security level (main+conference) will vary as they move from conference to conference. Entry # 10 - Additional Conference Time Allocation (0) (Definable) ------------------------------------------------------------------------ This is the additional amount of time a caller is granted (in minutes) when they join a conference. The program will only add the additional time in once. The time is NOT taken away from the user if he exits to the main board. If a caller is registered in two conferences, one which gives an additional time extension of 20 minutes and the other gives 10 minutes, they will not get the higher of the two. They will get the amount of the conference they join first - irreguardless of the time subsequent 7 - 4 PCBoard Chapter 7 December 22, 1985 conferences provide. If the caller first joins a conference where NO additional time is added and then joins one where there is time added, they will NOT receive the second conference's additional time. The program tries to add time to the caller's level one time only. A D D I T I O N A L C O N F E R E N C E I N F O ----------------------------------------------------- You must also have two files called CNFN and CNFNG in the '\GEN' drive\subdirectory of your system. These files should contain the menu information which will be displayed when a caller enters the "J" command at the command line. This filename is hardcoded into the program and can not be changed by you. Only 9 conferences are allowed using this software. This figure was chosen for several reasons. First, using a single digit integer between 1 and 9 made it relatively easy to store and examine conference registration information. Second, since space inside the user's file was limited, only three single digit registration characters were to be stored. Third, any board which tries to maintain over 9 conferences is not doing it's callers justice. If you need that many different conferences, it is questionable whether you are supporting your callers at a proper level. DO NOT ASK FOR or SUGGEST adding additional conference support to this software! It will not be modified to support a greater number of conferences - either in total or in the number in which a caller can be registered. Pick one, two or three main topics to support. Your callers and you will be pleased with the results. Last, you are limited in the number of below Ascii 48 characters which you can use for conference file protection. Again refer to your DOS or Basic manual for valid filename letters below Ascii 48 or use the ones provided as prompts by the PCBSETUP program. 7 - 5 PCBoard Chapter 8 December 11, 1985 E S T A B L I S H I N G D O W N L O A D S E C U R I T Y ------------------------------------------------------------- "FSEC" is the name of the file used to store download file security information. The file should be maintained and built using a text editor. It must be located in the '\MAIN' drive\subdirectory location. If you are presently running RBBS, you can use your current file with a simple modification. Simply remove all drive designations from the file names (including the colon), and in front of the filename insert a path location - followed by a comma - to designate it as another variable in the line. For example, if you presently have an entry in your RBBS file which reads... D:BASCOM.EXE,50, you would need to change the line to read... D:\,BASCOM.EXE,50, In other words, the path is a new variable at the beginning of each line entry. The '*' wildcard can still be used as normal. For instance - to protect all the 'private' sysop download file(s), you could have a line reading... ,PRIVATE*,100, Note that if you do not specify a path, all files on the system in the download path passed to the program in the main PCBOARD.DAT file will be included in the check. In the case of the BASCOM.EXE file example above, only the file on that drive would be checked. If the file was found on another drive before getting to the 'D:\' drive, the file security check indicated above would not be used and the file could be downloaded. You can also specify subdirectory information in the path as well. For example, an entry of ... \PCB\SYSOPS,*.*,100,TEST would mean all files in subdirectory '\PCB\SYSOPS' would require a security level of 100 or higher, and the user would have to enter the password of 'TEST' in order to download the file. CAUTION!!! THE DRIVE\SUBDIRECTORY INFORMATION IN THE FSEC FILE MUST MATCH YOUR DOWNLOAD PATH STRING EXACTLY IN ORDER FOR FILE PROTECTION TO BE ACTIVE!! IF YOU SPECIFY 'F:\S' IN YOUR DOWNLOAD PATH AND ENTER JUST A '\S' HERE, THE TWO WILL NOT MATCH AND THE FILES YOU ARE TRYING TO PROTECT WILL NOT HAVE PROTECTION PLACED ON THEM!!! The actual format of the each line of the file is... <drive\path>,<filename>,<security level>,<password> If a password is specified, the user will have to enter the proper password in order to download the file - even though their security level is greater than or equal to that required. If the user's password is the same as the download password, they will not be asked to enter the file's password. If their security level is less than the level indicated, they will not even be 8 - 1 PCBoard Chapter 8 December 11, 1985 asked to enter the password - they will simply be denied access to the file. When building this file, be sure and place your file security entries in proper order. For example, this board has several files on it which start with the filename of PCBOARD. The only file which user's are presently allowed to download is PCBOARD.DOC. Therefore, in the FSEC file I have two entries which read... ,PCBOARD.DOC,50, ,PCBOARD.*,100, The first entry allows the PCBOARD.DOC file to be downloaded by all callers inside the sysop's conference. The second entry restricts all callers except those with a security level of 100 or greater from downloading any of the other PCBOARD files. When building your download security file, make absolutely sure that the drive\subdirectory locations in the file EXACTLY match those of your download path in the PCBOARD.DAT file or file protection on those files in the security file will NOT be effective. 8 - 2 PCBoard Chapter 9 December 22, 1985 E S T A B L I S H I N G U S E R T I M E A L L O T M E N T S -------------------------------------------------------------------- "PWRD" is the name of the file used to store the security level and time allowed information for callers. It can also include any logon password information you may wish to specify. If you are presently using RBBS, you can use your present PASSWORD file without modification. If you are not running RBBS, the file should be built using a text editor. CAUTION: You must have a matching security level for every level assigned to a user inside your data base!! Each line of the file consists of the following... <password>,<security level>,<time allowed (minutes)> For example, to grant all users with a security level of 50 seventy-five minutes of time, your entry would be... ,50,75 If you had a group of callers who all used the same password in order to get special time on your system, you may need an entry such as... SYSOP,75,120 where any user whose password was SYSOP and whose security level was 75 would be granted 120 minutes on the system. When converting or building your password's file, make sure that no password is greater than 12 characters. If it is, you will get an error # 5 in line 6900 when you try and logon to your system. Also, you can only use single word passwords in the file. If you fail to have a corresponding entry in this file for each security level assigned to your various users, the user's time for that call will default to 10 minutes. The program will not try and find a happy medium between two levels in this file to give a user who's security level does not have a match here. Therefore, be sure you have a matching entry here for every security level you use and assign to your callers. 9 - 1 PCBoard Chapter 10 December 22, 1985 S C R I P T Q U E S T I O N N A I R E F I L E S ----------------------------------------------------- The software supports a main and individual conference "script" questionnaires which can interrogate the caller on a multitude of subjects. A text file called ASK.DAT or xASK.DAT (for conferences) must be present for the function to work. Responses which the user leaves are placed in a file called ANSWER.DAT or xANSWER.DAT (for conferences). Note that the 'x' above is the first letter of the name of a conference if a conference questionnaire is active. The ASK.DAT file consists of five 'header' lines, plus your questions. The five header lines should briefly explain the purpose of the questionnaire. CAUTION: You must have the five lines - even if they are blank! The program will insert a blank line before and after displaying the five header lines for you - so you can fill up all five lines to their capacity if desired. Following the header, you should enter the questions you wish to ask. For example, let's say you have a questionnaire active in the sysop's conference in which you wish to poll the other sysops on whether a board should be 'public' or 'private'. A sample of the questionnaire might be... ------------------------------------------------------------------------ **************************************** *** Sysop's Conference Questionnaire *** *** Public or Private? *** *** Please answer all the questions! *** **************************************** Go Public (Yes/No) Would you pay for access (Yes/No) If yes, how much Is your board public (Yes/no) If private, why What's the name of your board And it's number Have you honestly answered above Why not!! ------------------------------------------------------------------------ The questions following the main header can be any length - but should be kept short and to the point. The program allows a 60 character response to each question. You can have as many questions after the header block that you desire! After the last question, the caller will be advised his information has been entered. Data actually written to the ANSWER.DAT file is written in the format... 10 - 1 PCBoard Chapter 10 December 22, 1985 ------------------------------------------------------------------------ ***[Sysops Conference Questionnaire Information]*** From: JOHN DOE Date: 09-17-85 Time: 10:30 <question>: <answer> <question>: <answer> <question>: <answer> <question>: <answer> <question>: <answer> etc... ------------------------------------------------------------------------ There is no upper limit on the size the answer file may grow to. Use caution and purify it regularly! Since each conference may have it's own questionnaire, you can easily get confused with all the information you receive! Keep this function in check. 10 - 2 PCBoard Chapter 11 December 22, 1985 C A L L W A I T I N G M E N U O P E R A T I O N -------------------------------------------------------- Shown below is a representation of the main sysop's system screen while waiting for a caller to access the system: +----------+---------------------------------------------------+----------+ | 12-22-85 | PCBoard Software - Ver. 9.0 - 12/21/85 | 10:00:00 | +----------+---------------------------------------------------+----------+ Sysop Into System (Phone Busy) Local User Logon (Phone Busy) Exit to DOS (Phone Busy) Exit to DOS (Phone NOT Busy) Toggle Line Printer (On/Off) Toggle Caller Alarm (On/Off) Toggle Page Bell (On/Off) Use [F9] to Toggle Display (On/Off) +----------------------------+--------------+------------+----------------+ | Status: System Available | Printer: Off | Alarm: Off | Page Bell: Off | +----------------------------+--------------+------------+----------------+ | Make a selection using the | and | keys. Press [ENTER] to execute. | | (C) Copyright 1985 - Clark Development Company, Inc. | +-------------------------------------------------------------------------+ To execute a function using the menu, the sysop should simply use their up and down arrow keys to highlight the desired selection, followed by pressing the [Enter] or [Return] key. Additionally, the current function key assignments used by older versions of the code still work at this menu. They are: [Esc] - Sysop Into System (Phone Busy) [F1] - Exit to Dos (Phone Busy) [F2] - Local User Logon (Phone Busy) [F3] - Toggle Line Printer (On/Off) [F4] - Toggle Page Bell (On/Off) [F7] - Toggle Caller Alarm (On/Off) [F9] - Screen Display (On/Off) [F10] - Exit to DOS (Phone NOT Busy) The status of the line printer, page bell and caller alarm are now shown in small boxes near the bottom of the screen with the word either "On" or "Off" next to their name to indicate their status. The [F9] function key must still be used solely to change from screen display on to off and visa versa. A prompt on the bottom of the screen advises you of this fact. When the screen clears after three minutes, the only keys which remain 11 - 1 PCBoard Chapter 11 December 22, 1985 active are the [F1], [F9] and [F10] function keys. If you press one of these keys, the function will immediately be performed. By pressing any other key, the main menu will be re-displayed before the key will actually function. This is to help prevent inadvertent actuation of a function not desired. During this main menu display, the current date and continuously updated time are also shown - except during modem reset and recycling. 11 - 2 PCBoard Chapter 12 December 22, 1985 S Y S O P F U N C T I O N K E Y A S S I G N M E N T S -------------------------------------------------------------- Once inside the program, the 24th line indicates the baud rate of the current caller, the caller's name, the caller's city and state, the time the caller logged on to the system and the current time of day - which is continually updated throughout the program. The 25th line of the program displays the last date the caller was on the system, their number of times on, their conference registration information, their security level (including a CS for conference security indication), the number of uploads and downloads they have performed, and the letters (P) for printer on, (A) for caller alarm on and (B) for page bell on. The prompt [Home]=Help means that you can press the [Home] key to change the 24th and 25th lines to help lines - indicating the functions performed by the 10 function keys and [Alt] keys. By pressing the [Home]=Help key, the bottom two lines change to... Alt-> F=File Out I=File In N=Next On P=Print On T=Form Feed 10:00 10:00 1=SyPrv 2=LkOut 3=Prnt 4=Bell 5=Shell 6=Reg 7=Alarm 8=HngUp 9=Screen 10=Chat This line can be brought up at anytime during program operation. The Sysop can return to the normal status line by pressing the [End] key. Additionally, the screen will change back to normal status after the user selects or performs a system function. The program also allows the sysop to view the caller's two phone numbers and their password by pressing the [PgDn] key. The use of the [PgDn] key is especially helpful when logging on in local mode as a user if you forget the user's password. After entering the user's name, simply press the [PgDn] key to display their password for continued logon. If a caller is inside a conference, the "S=50" portion of the 25th line prompt is changed to "CS=50" so that the sysop can quickly see the caller is inside a conference. While waiting for a call, the function keys available to the sysop are: Esc - Places the phone 'off-hook' (busy) and asks you for your 'local' password (PASSWORD1) in PCBoard.DAT. By entering the proper password, you are logged into the sysop as 'The Sysop'. F1 - Places the phone 'off-hook' (busy) and exits to DOS. There is a two second delay before the phone is placed 'on-hook' after pressing the [F1], [F2] or [Esc] keys. This is to allow enough time for the modem to go 'off- hook' before allowing you to enter the program. F2 - Places the phone 'off-hook' (busy) and asks for the user's name as if carrier detect had been established. This allows a sysop to check the system operation as if it were actually a caller on-line. All functions which would generate an error from trying to "print" to the communication's port are properly trapped to allow the sysop to check for most board functions. F3 - Toggles the local line printer off/on. Line 25 of the screen will display the current status. F4 - Toggles the page bell off/on. The sysop is ALWAYS paged if the user 12 - 1 PCBoard Chapter 12 December 22, 1985 requests it and has sufficient security. ONLY the bell can be turned off/on. F5 - Not active. F6 - Not active. F7 - Toggles the alarm off/on which sounds when a caller first gets on-line, when they enter the main part of the board, and when they attempt an invalid function or selection. F8 - Not active. F9 - Clears screen and turns off ALL future display until re-pressed. F10 - Exits the sysop to DOS but does not place the phone 'off hook' or busy. In this case, incoming calls will not get a busy signal when they call your system. After a caller is on-line, the function keys perform the following: Esc - Allows exiting from Chat mode if active. F1 - Toggles temporary sysop privileges for that caller on and off. F2 - Disconnects caller, locks them out, hangs up phone. F3 - Same as 'waiting' screen above. F4 - Same as 'waiting' screen above. F5 - Allows sysop to exit to DOS using the SHELL command. F6 - Allows sysop to update user data base/security status while the caller is on-line. F7 - Same as 'waiting' screen above. F8 - Automatically disconnects the caller and resets the board. F9 - Same as 'waiting' screen above. F10 - Forces chat mode by sysop. The [Alt-N] key combination allows a sysop to set a flag which will allow him to be the next caller in the system. By pressing [Alt-N] while a caller is on-line, a flashing "*" will appear between the two time displays on line 23 indicating the sysop will be the next into the system. By pressing [Alt- N] again, the flag will be removed. The [Alt-P] key allows the sysop to "capture" to the local line printer all the program information displayed on his terminal while on line in local mode as either the sysop or as a "local" user. This allows saving to printout all messages, etc. for later review. To use this function, the sysop should enter an [Alt-P] at the main command line before reading 12 - 2 PCBoard Chapter 12 December 22, 1985 messages, etc. Once activated, all screen display (except "More:" prompts and user keystrokes) will be sent to the local printer. This function is toggled "off" every time the main command line prompt appears. After pressing [Alt-P], a "P" will appear next to the logon time on the 24th line indicating the local printer will be echoing all screen display. By pressing [Alt-P] again, the printer will be toggled off-line and the "P" will disappear. During printer output, a 4 space left margin is used to allow for binding in a three ring binder. Also, the program will automatically insert page breaks during local printout of text. In order to begin a local printout session, the sysop should position the printer's paper approximately 3 lines down from the top of the perf. The program will automatically place a 3 line margin at the bottom and top of each consecutive page printed. The [Alt-F] function key allows the sysop to "echo" the screen display to an Ascii text file on disk - similar to the [Alt-P] function described above. In this case, the output is sent to an ascii file which has the name of the current message base in effect plus the suffix ".TXT". For instance, using this function while reading messages in the main section of the board will send the output to a file called "MSGS.TXT". If this feature was used inside a conference - such as the SYSOPS conference, the output would be called SYSOPS.TXT. This feature allows the sysop to save to disk (in ascii format), messages, etc. which then can easily be transported to other systems. During disk file output, the 4 space left margin is not written to disk. The [Alt-I] key allows the sysop to "import" a text file from disk for placement inside a message - rather than having to type one in at the screen display. To use this feature, you should first initiate the message entry procedure by entering [E] at the main command line. Next, properly address the message and give it a subject title. Then, when the line entry screen appears, press [Alt-I]. This will bring up a highlighted line on the top of the screen which will ask you to input the name of the file you want to merge into the message. You can use paths in the response. If the file is found, it will automatically be "loaded" into the message. If it is not found, an appropriate error message will appear. You can then make an additional request or just enter the message manually. The file to import should already have been properly formatted using a text editor prior to using the [Alt-I] function. Although the program will attempt to handle long lines, etc., you should have the file already setup for merging which will not require the program to try and format it as it reads it in. By using the [Alt-F] and [Alt-I] functions, it is relatively easy to move messages around between systems, etc. Additionally, you can request the [Alt-I] function at any point while entering a message. For example, if you wish to preface the import with several sentences, this can be done- followed by the actual import. If the message you are trying to import has too many lines in it for the program to handle, the code will drop the extra lines from the import procedure automatically. The [Alt-T] function allows the sysop to send the local printer a "Form Feed" character - which will eject a page from the printer. This function is available at all times during program operation. 12 - 3 PCBoard Chapter 13 December 22, 1985 P R O G R A M M E N U S E L E C T I O N S ----------------------------------------------- Shown below is a sample of the main menu - including all sysop functions. ------------------------------------------------------------------------ ==[ Salt Air Sysop's Menu ]============================================== 1)Display/Print Comments 6)Delete All Comments 2)List/Print Users/Callers 7)User Maintenance 3)Pack/Renumber Messages 8)Pack the User's File 4)Recover a Message 9)Exit to DOS (Remote) 5)List Message Headers 10)Perform DOS Function A)bandon Conference G)oodbye (Hang-Up) M)ode (Graphics) T)rans. Protocol B)ulletin Listings H)elp Functions N)ew Files(Date) U)pload a File C)omment to SYSOP I)nitial Welcome O)perator Page V)iew Settings D)ownload a File J)oin a Conference P)age Length W)rite User Info E)nter a Message K)ill a Message Q)uick Msg Scan X)pert On/Off F)ile Directories L)ocate Files(Name) R)ead Messages Y)our Per. Mail S)ystem Questionnaire Z)ippy DIR Scan ------------------------------------------------------------------------ Sysop Menu Functions -------------------- 1 - Item number 1 allows the sysop to view and/or print out the comments left to him from the callers. If the print option is selected, the printout goes to the board's local printer - not the remote printer!! If the local printer is off-line, the program will recover. However, use caution when printing the file to your printer from a remote location and then deleting the file. You may loose the file in the process. All sysop printing functions inside the code default to continuous or non-stop displays - meaning you do not have to enter the [NS] command to have the file completely printed out. The printout to the local printer includes a 4 space left margin and intelligent page breaks. You should first do an [Alt-T] to send a form feed to the printer to insure you are at the top of the page. Next, make sure the perf is about 3 lines down from the top. Then begin your print option. 2 - This function allows the sysop to view the user list which will display all users - including their name, last date and time of logon, and the amount of time they used during the last day they were logged on. You can also select to view the caller log using this option. If selected, the caller log will be displayed in reverse order it was written. (i.e. Most recent callers first) Optionally, you can print out either the user list or caller log to your local printer after selecting this option. This allows you to leave your printer off during normal board operation, while still allowing you to easily printout the complete caller log when needed for archival purposes. You can also delete the called log when selecting this option. If you delete the log, a new caller log is started with information in the file indicating the date and time it was initiated. The caller log contains substantially more information about a caller's activities than does RBBS. As a result, the file 13 - 1 PCBoard Chapter 13 December 22, 1985 can quickly grow to tremendous size! Please keep a handle on the size of this file and archive it to hardcopy output regularly - initiating a new log file after completing the report. 3 - Allows you to pack and optionally renumber the message base you are using. For example, if you are in the main section of the board, the main message base will be packed. If you are inside a conference, the conference message base will be packed. NOTE: When first running PCBoard it is necessary to enter one message, followed by packing the file. This will properly initialize all message number pointers. If you indicate you wish to pack the message base, you will be asked to input the date of the oldest message you wish to keep, and if you wish to renumber the message base during packing. If you do not enter an 'oldest' date, the program will default to 010180. (i.e. No messages will be purged because of the date check.) If you decide to renumber the message base, you should enter the new beginning number of the first message you wish to have displayed after renumbering. (i.e. If you input the number 100, all messages will be renumbered starting at 100 and will be incremented by one up to the number of active messages). To skip the renumbering option, just press [C/R] at the appropriate prompt. Note that during message repack, all function keys are disabled. 4 - Recover a Killed Message allows you to re-activate a previously killed message. Prior to selecting this option, you should use menu selection 5 below to determine the message number that is to be restored. If the message base has been repacked, all killed messages will be inside the 'MSGS.BAK' file - not the active 'MSGS' file. In that case it may be necessary to copy the backup message base on top of the current base. Use EXTREME caution when doing this however, and have a complete backup of your messages before beginning! 5 - Allows you to view the message 'header' block of all active and inactive messages in the message base. The program will properly pause at the appropriate times to prevent any loss of data from the top of your screen. 6 - Allows you to delete all comments. 7 - User maintenance provides a means of adding or modifying callers in the user's file, and of producing a visual or hardcopy output of the complete data base information on all registered users. If you select [A]dd new user's, you will be asked to input the user's name, city and state, password, business/data phone number, home/voice phone number, security level, conference registration information, and transfer protocol. If you are modifying a user's data, select [A]lter after the [M]odify prompt. During user data base information updating, you can simply press your [C/R] to skip over an item in the data base without altering it. This same form of data input/update is used when using the [F6] Registration function key while the caller is on-line. Be aware that the caller can see your keyboard entries on their screen as you are performing their update. Note that they can also assist you in the update process by entering information themselves - such as their password. You can also search for user's by a name or user number search. Please note that the software does an EXACT name search at ALL times - including message 13 - 2 PCBoard Chapter 13 December 22, 1985 reads, etc. This is to prevent a caller named JIM JOHN from reading mail addressed to JIM JOHNS. If you wish to mark a user for deletion, press [D] for delete. When this is done, the user's security level is changed to "0" and a special flag is set which will cause a force 'purge' during the next user file pack. If you wish to 'undelete' a user, simply press the [U] key. This will remove the forcible delete flag, but it will NOT up the user's security level. You will need to select [A]lter to re-establish an appropriate security level for the caller. 8 - Pack User's File allows you to pack the user's file and to 'purge' those user's you desire. After selecting the option, you can choose from several packing criteria - including whether to keep all user's whose security level is "0" (locked out) - irreguardless of the other options selected; to purge user's whose last date on the system is older than that which you specify (defaults to 010180); and finally you have the option of keeping all user's whose security level is greater than or equal to an amount you specify (defaults to 100). In other words, if the 'delete' user flag is set to "Y", a user will automatically be deleted. If you decide to keep all 'locked out' users, they will not be checked against the date input. Likewise, users whose security level is equal to or greater than that specified will not be purged based on the date criteria. The lowest priority purge is based on the date, with the highest being the force delete flag. If you wished to purge all users who had not met your registration requirements (i.e. they had a security level equal to the 'refused to register' level from the PCBoard.DAT file), but you wished to keep all registered users and all locked out users, you would respond as "yes" to keeping all locked-out, input the lowest security level allowable for registered users, and input the current date as the 'oldest' from which to purge. This would clean up your user's file - keeping only current registered and locked-out users. Note that during user data base repack, all function keys are disabled. 9 - Allows you to exit to DOS from a remote location. The batch files used to allow exiting to DOS from remote are BOARD.BAT and REMOTE.SYS. BOARD.BAT should normally contain the following with additional items as you desire: ------------------------------------------------------------------------ c: cd\pcb if exist remote.bat rename remote.bat remote.sys if exist event.bat rename event.bat event.sys if exist endpcb del endpcb pcboard if exist remote.bat remote if exist event.bat event if exist endpcb goto end board :end cls^Z ------------------------------------------------------------------------ The file above works like this: 13 - 3 PCBoard Chapter 13 December 22, 1985 1. "c:" - Switch to your "default" physical drive to make sure you go back into the board from the right drive. 2. "cd\pcb" - Switch to the proper subdirectory on that drive. 3. "if exist remote.bat rename remote.bat remote.sys" - If the file REMOTE.BAT is found (i.e. You or someone else exited to DOS using the [F9] function key - at which time the file REMOTE.SYS was renamed to REMOTE.BAT by the PCBoard.EXE program), the file renames it back to REMOTE.SYS so upon exiting the program later, it will not think you are once again exiting from remote. 4. "if exist event.bat rename event.bat event.sys" - If the file EVENT.BAT is present because of an event timer routine, the file will be renamed to EVENT.SYS before entering the program. This is to prevent running the EVENT.BAT file unless actually directed to by the program when it next exits to DOS. 5. "if exist endpcb del endpcb" - Clears the file ENDPCB from the drive. This file is created when you properly exit the main program using the [F1] function key while waiting for a call. 6. "pcboard" - Runs PCBoard. 7. "if exist remote.bat remote" - Checks for the presence of the REMOTE.BAT file (which is the file REMOTE.SYS renamed by the program to REMOTE.BAT just before exiting to DOS from remote). If the file is found, it is assumed you have exited to DOS from remote and the file itself (REMOTE.BAT) is then run - in effect exiting the BOARD.BAT file at that time to run REMOTE.BAT - which when it finishes will re-run BOARD.BAT. 8. "if exist event.bat event" - checks for the presence of the file EVENT.BAT, which was created by the program by renaming EVENT.SYS just before exiting under the event timer. If the file is present, that batch file is called up to perform it's respective function(s). When it is finished, it should recall BOARD.BAT. 9. "if exist endpcb goto end" - This line checks for the presence of the file ENDPCB - which is created by the program when you exit using the [F1] function key. If it is NOT present, it means the code has dumped to DOS under other than proper conditions. If the file is not found, the batch file "falls through" to the next line - "board"- which re-runs BOARD.BAT. This then will restart your system. If the file is found, it jumps to the label ":end" - which finally terminates the BOARD.BAT batch file. 13 - 4 PCBoard Chapter 13 December 22, 1985 The REMOTE.SYS file (which is called up by BOARD.BAT above if you exit to DOS from remote) should contain: (Example shown for COM1) ------------------------------------------------------------------------ watchdg1 on ctty com1 echo Sysop into DOS from Remote echo Type 'Exit' when finished command ctty con watchdg1 off board ------------------------------------------------------------------------ CAUTION: You must 'Exit' back to the program from the default drive location. If you type exit from a location other than where you left the program at, you may get errors in your file locations when re-entering the program. As a safeguard, you should put a statement in the beginning of the BOARD.BAT file to place you back in the default drive\subdirectory location just in case you forget. (See example above.) CAUTION: You can not use the remote function running under Multi-Job and some other multi-tasking software because of the new compiler. If you do - your machine will lock up. Just prior to exiting to DOS, you will be asked to specify a password which the program will require that you input upon returning from your DOS level work. This password can be anything you want, as long as it is one word of 12 characters or less. This feature was built in to prevent someone else getting into your system as you in case something were to happen while you were in DOS which caused your board to recycle with the next caller jumping in where you left off! This password is not fixed and must be specified every time you exit. 10 - An additional sysop function selection - # 10 - can be used to quickly enter and execute DOS commands from inside the program. This allows the sysop to perform quick and dirty DOS functions - like copy commands - from a remote location without requiring the use of the [F9] remote function. In this way, a simple DOS function can be performed without having go into the system from remote. CAUTION!!! CAUTION!!! You will not be shown the status of the DOS function being performed. Also, if the function you initiate requires a keyboard response, your machine will be LOCKED UP!! This command is ONLY to be used for very simple functions - which even if not properly executed - will return back to the normal DOS prompt - which will in turn return control of the machine to you. If for example you request a copy from a floppy drive in which there is no disk inserted, DOS will issue the message "Abort, Retry, Ignore" and wait for a response from the keyboard - which you are unable to give it. Therefore, your machine is hung. Even by hanging up at the remote location, your board will NOT re-cycle. Use EXTREME caution when using this menu selection!! For example, it is possible to use this function in local mode to call up another program while inside PCBoard. (i.e. Your text editor) When 13 - 5 PCBoard Chapter 13 December 22, 1985 finished, you would be placed back inside the board's code. However, if you were to execute the same command from a remote location, you would loose control of your machine and it would not recover until you could get to your keyboard to exit the text editor! 13 - 6 PCBoard Chapter 13 December 22, 1985 User Menu Functions ------------------- Note: In all examples below of stacked commands, the caller can optionally use a space in place of the semi-colon ";" as their stacked command delineator. [A]bandon Conference - Allows the caller to leave an active conference for the main board. [B]ulletins - Brings up the BLT, BLTG, xBLT or xBLTG menus displaying current bulletin information. If none are available, the program so advises the caller. Bulletin numbers can be stacked after the [B] command. Maximum number of bulletins is 99. Bulletin numbers can also be stacked at the number prompt in the format "x;x;x" if desired. If the caller places a leading "b" in front of the bulletin numbers - it will be filtered out by the program. If a caller is in novice mode and stacks a bulletin request, the program will pause after the last bulletin is displayed before re- displaying the main menu. [C]omment to Sysop - First checks to see if the comments file is not too large already. If it is, the user is advised they cannot leave a comment. If it isn't too large, they can enter a comment to the sysop. The entry format and editing commands are the same as during message entry - with the exception that the word 'comment' is used in place of 'message' for most program displays. Comments are stored in an ascii file which can be 'typed' to your screen or printer, or printed out by using the # 1 sysop function inside the program. Comments are limited to the maximum number of text lines as defined in PCBSETUP. [D]ownload a File - Prompts the caller to enter the name of the file they wish to download. All caller entries are checked for invalid filename requests and proper file security levels. The screen will display current download information, including transfer time and size, and the total amount of bytes transferred during that call - to help out floppy disk user's keep from running out of disk space. The sysop's file transfer display is non-scrolling - with block number, number of consecutive errors, and total errors shown on one line during transfer. The sysop can use all function keys during file transfers - including the [Home] key for help. Transfers automatically abort if they are not started in 40 seconds. Transfers also abort if the number of consecutive errors for one block exceeds 10. The total number of file transfer errors are written to the caller's log along with the file completion status. [E]nter a Message - Allows the caller to enter a message into the message base - either main or conference - depending on their location. The caller is prompted throughout message entry as to where the message is going. The user can edit messages entered prior to [S]aving them to disk. Reference message numbers are stored with messages which are generated using the [RE]sponse command. Message numbers are not limited to 9999 - they can grow up to # 65000. However, only 400 message numbers can be 'active' at any given time. You can specify the maximum number of message lines allowed per 13 - 7 PCBoard Chapter 13 December 22, 1985 message (up to 60). Note: When requesting the [E]dit, [D]elete, or [I]nsert editing functions during message or comment entry, the space (" ") will NOT work as a delineator. This is to prevent possible conflicts between the user's command and their actual text. Frequently the caller may have difficulty in uploading an Ascii file to the message base. The problem is usually in the software they are using. They fail to set the proper timing sequences for the message to be uploaded properly. When using Qmodem, the upload should occur by waiting for the ":" prompt. PibTerm can be set to a 10 millisec delay between lines. These two common settings will help most callers send up the file properly. [F]ile Directories - This displays the file DIR, DIRG, xDIR or xDIRG - which contains the listing of all the file directories available. To view a given file directory listing, the caller simply needs to enter the appropriate number at the prompt. Specific directory listings can be requested from the main command line using the stacked command "f;x;x" where the 'x's are the actual directory numbers. The caller can also stack the numbers at the file listing prompt in the format "x;x;x". They need not re-enter the "f" at this point. However, if they enter a leading "f" or "l", the program will automatically filter it out. If the caller is in novice mode and uses a stacked command, the program will pause after the last display before bringing up the main menu. The caller can request a download directly from the directory number prompt. This request can be either just the letter [D], after which the caller will be prompted to enter the filename, or the caller can stack their request in the same format indicated in [D] above. [G]oodbye - Disconnects the caller and re-cycles the board to await the next caller. [H]elp Functions - Allows the user to bring up one of the 26 help files available for each of the menu commands. [I]nitial Welcome - Re-displays the main welcome screen - either in graphics or non-graphics mode - depending on the mode the caller has currently specified. The program allows for the two 'WELCOME' files to be longer than 23 physical lines - so that you can incorporate extensive color displays in the file without getting a "More - ..." prompt in the middle of the file. These are the only files which provide for this 'non-stop' type of display automatically. All others will be handled by the page length set by the user - normally 23 lines. Which means that if a file is 22 lines in length - the caller will not get a "More - ..." prompt. If it is 23 lines long - they will. The version number and date of the code will also be displayed along with the welcome file itself. 13 - 8 PCBoard Chapter 13 December 22, 1985 [J]oin a Conference - Brings up the CNFN or CNFNG files which display the current conference(s) available. From the conference number prompt, the user should enter the number of the conference they wish to join. They can stack their join request at the main command prompt in the format "j;x". [K]ill a Message - This allows the caller to kill one specific message on the board. They will then be asked to enter the number of the message they wish to kill. If they do not have the proper security clearance to kill the message - they will be so advised. They can stack the kill command at the main command line in the format "k;x" where 'x' is the message number to kill. [L]ocate Files(Name) - This command allows the caller to scan the file directory listings using a wildcard name search. The program only supports the '*' wildcard - not the '?'. For example, to scan for all files which start with the letters "DIR", the caller would normally enter the filename request as "DIR*.*". If the user requests a "*.*", all files in the listing requested will be displayed. The caller can request a scan on an individual directory, a group of directories, or all directories. At the number prompt, they should enter just the single number of the listing desired. They can stack the numbers in the format "x;x;x", or by entering an "a", the program will scan all the directories available. If a caller is inside a conference, the conference directories will be scanned as well. If they are outside a conference, it will only scan the main board listings. The caller can also stack the [A] request at the main command line following the [L] command (i.e. "l;a" tells the program that a filename scan is to be conducted on all directory listings). The caller will then only be prompted for the search filename. NOTE: If you have not properly set up your directories with a period between the filename prefix and suffix, this command will not work properly. [M]ode (Graphics) - This command allows the caller to switch between ANSI.SYS color graphics mode and non-graphics mode. However, the PCBoard software always drives through the ANSI.SYS driver - whether the caller is in graphics mode or not. When the caller selects graphics mode - all text is run through an internal program string processor which places the necessary chr$(27) color codes into the string for output. When graphics mode is de-selected, this string processor is bypassed - outputting the text in unmodified format. Once a caller has selected graphics mode, all future non-graphic displays to the sysops screen will be in the intensity and color specified in PCBSETUP. Prior to that, they will appear in the last color sequence sent through the ANSI.SYS driver in DOS. For example, if you "typed" a color graphics file to your screen that ended in setting the color to red on a green background, the initial non-graphics displays of PCBoard will come up in red! To insure proper initial color setting, you should 'type' a small file to your screen at the DOS level before actually entering PCBoard. The file should contain the following command... chr$(27)+"[00;33;40m" Use your normal text editor to generate the chr$(27) code in front of the "[00;33;40m" code. 13 - 9 PCBoard Chapter 13 December 22, 1985 NOTE: If your 'non-graphics' flag is set to "Y", it is not necessary to load in ANSI.SYS, or to have a "G" (graphics) versions of the previously discussed files available on your system. In this case, all colors in the code default to white and bright white - and no graphics files are accessed. Also, all text is outputted to the sysop's screen using a PRINT statement rather than through the ANSI.SYS driver. [N]ew Files (Date) - This command allows the user to scan the file directories based on a date check. The number of the directories to be scanned should be entered as in [L] above. In this case, the caller should enter the date in "mmddyy" format from which they want the scan to begin. All files in the directory listings which have a file date equal to or greater than the date requested will be displayed. The caller can stack the [A]ll prompt onto the [N]ew prompt at the main command line. Then the program will simply ask for the date. (i.e. "n;a" will tell the program the caller wishes to perform the [N]ew command on all directory listings.) The date of the check will default to the last date on which the caller looked at any of the file directories. For example, if they have logged on twice in the last week, but did not look at any file listings, their default scan date may be a date from several weeks previous - at which time they did do an [F] command. New user's default to the date '010180'. [O]perator Page - Allows the caller to page the sysop. There is no 'allowable' time span for the page to be effective - it is always operational if the user's security level is equal to or greater than that required to perform the [O] command. The sysop can of course turn on/off the page beep which summons him to the machine. The caller can abort the page at any time by pressing [Ctrl-K]. To respond to a page request, the sysop should press the space bar on their machine. During chat mode, the caller's time used is placed 'on-hold'. [P]age Length - This command allows the caller to set the number of lines which will be displayed on their screen before a "More -" prompt appears. The maximum number which they can specify is 25. The default # is 23 - which means that callers will be displayed 23 lines of text, followed by the "More - " prompt on line 24, with their line 25 being handled by their software. Caller's whose software uses both line 24 and 25 will need to set their page length at 22 to prevent the top line of the screen scroll display from disappearing before the "More - " prompt appears. (This is for users who are using SCOM.) If the user specifies a page length of 0, no "More -" prompts will ever appear - screen display will always be continuous without pausing. [Q]uick Message Scan - Allows the caller to scan the message base by message number, reference message number, and subject. The user should enter the lowest message number to begin the scan from at the appropriate prompt. Messages which are protected will not be displayed. [R]ead Messages - Allows the caller to read messages in the message base. The caller can enter one specific message number to read, or a group of 13 - 10 PCBoard Chapter 13 December 22, 1985 numbers by using a complete set of "movement" commands. The heart of the new command procedure is a routine which "scans" the user's requests and attempts to process those requests - irreguardless of the order in which they are entered. The basic command structure to read or scan messages is comprised of six main commands: A: [R] for read B: [S] for since last message # read (old "*" command) C: [Y] for mail addressed to you D: [F] for mail from you E: [N] for read the next higher message F: [P] for read the next lower message Here are some examples: R S [R]ead all new mail [S]ince you last logged on (just like R;* which also still works). R Y [R]ead [Y]our mail, that is, all mail addressed to you. R S Y Read all new mail addressed to you. R Y S Same thing -- the order doesn't count. R Y 250 Read all mail addressed to you higher than number 250. R 250 Y Same thing. R F [R]ead all mail [F]rom you to others (you can check to see if a message has been received and/or kill it if it has become outdated). R F 250 Read mail from you to others higher than number 250. R 250 F Same thing. R F Y Read all mail from or to you. R F Y 250 Read mail from or to you higher than number 250. Other combinations of [R] and its subcommands will work as well. PCBoard will intelligently parse any combination, and return an appropriate "error" message if it finds nothing to read in response to your request. You can stack the commands, as shown above, or give them in response to the system's prompts. You can even use the "old" method of separating the commands with semi-colons, e.g. R;S;Y , but usually spaces instead of semi's are easier and PCBoard allows it. All the same commands work with [Q]uick Msg Scan as well. Please note that the [*] command will still function as normal - just like the new [S]ince command. However, the [*] prompt will no longer be displayed - since many new callers to most BBS systems had no idea what the [*] meant! The ability to read [N]ext and [P]revious messages has been added to the main Message Base Command Line. If a caller reads one message, and then is returned to the "Msg(s) [1 - xx]" command line, they can read the next 13 - 11 PCBoard Chapter 13 December 22, 1985 message in line by just entering an [N] for next. Or they can read the previous on by entering a [P] for previous. If they have not read a message and enter the [N] command, reading will start at the first active message. If they enter a [P], the main menu will be re-displayed. If the caller now just enters a "+" or "-" at the message read "More: " prompt, the code will recognize the request and begin processing forward or backwards - without the need on inputting a corresponding message number. If message read "Help" is requested, the caller will be returned to the Message Command Line rather than the Main Menu Command line as previously occured. The board uses a slightly modified message display header. It now displays the message date, who the message is to, who the message is from and the subject on the left side of the screen. The message number, reference message number, whether the message has been read by the receiver, and the message security level on the right side of the screen. If the reference message number is lower than the lowest active message number in that message base - the reference number will show "none". This was done to prevent callers from trying to read a message which was no longer available. If the caller enters a message number followed by a "+" sign, (i.e. 456+), all messages starting at number 456 and above will be displayed - pausing between each for caller review. By adding a "-" to the requested number, all messages starting at the requested number and below (in reverse order) will be displayed - again pausing between each for review. The code also supports [T]hread reading of messages. This allows a caller to read all messages associated with a "base" message. When the "More" prompt is displayed, the user will have an additional command of [T]hread- which allows setting the subject of that message as the base from which to scan all other messages. The caller can scan forward in the message base for all related messages by simply entering a [T]. If this is done, the program defaults to a "+" condition, and begins reading all messages from that point forward which have the same subject title. If the user enters a [T-], the program searches from that message backwards in the file for all subject matches. The user can go forward or back in the file as desired. The user can also specify a specific numeric message number at the "More:" prompt when reading messages if they desire to go to a specific message. [S]cript Questionnaire - Allows the caller to complete a system questionnaire if one is present. There can be a questionnaire for the main board plus each individual conference. They can vary in length based on the sysop's needs and are easily maintained using a text editor. User's answers are written to separate text files along with the questions asked - so that a questionnaire can vary and information stored in the response file can still be properly analyzed. [T]ransfer Protocol - Gives the caller the opportunity of specifying the default transfer protocol they wish to have written to their user record for all future calls. The choices available are [X] for Checksum Xmodem, [C] for CRC Xmodem, [Y] for Ymodem CRC, [A] for Ascii, and [N] for none. The caller can over-ride their default when initiating a file transfer by stacking the protocol desired after the filename at the main command line. For example, a caller whose default transfer protocol was [C], could request an Ascii download of the file by entering "d;<filename>;a" at the main 13 - 12 PCBoard Chapter 13 December 22, 1985 command line. If the caller tries to stack the transfer type on the "Enter the full filename to..." line, it will be ignored. [U]pload a File - Allows a user to upload a file to the board. If the caller is inside a conference, they will be asked if they wish to have conference security placed on the file. Conference security includes placing the file in the conference upload drive location and placement of the file's description in the conference upload directory rather than the main board upload directory. If you have also specified a special conference 'security' character in the CNAMES file, a file which is uploaded inside a conference on which the caller has specified that conference security is to be placed, will have it's filename changed to include the security character as the last letter of the filename. This will prevent future downloading of the file except to those callers who are physically inside the corresponding conference. The caller's default transfer protocol will be used for the transfer type. If the caller wishes to use a different protocol, they should stack their request at the command line in the format... u;<filename>;<protocol> Once the file has been checked against existing board files, the caller will be shown upload information - including drive status, upload placement, and upload status. In order for the program to properly display the upload drive status, it is necessary to include a logical drive location in your PCBOARD.DAT and CNAMES file(s). (i.e. an entry of "\UP" would not display any upload drive size information. An entry of "C:\UP" would.) CAUTION: If you as the sysop want to upload a file to your system which is already present on one of the download drive locations, you have the option of 'over-writing' the file. If you indicate you do wish to over-write it, the new file will be uploaded in the SAME drive\subdirectory location as the old file - it WILL NOT be placed in the normal or conference upload drive\sub location(s). This allows you to send uploads to the board to replace files which must stay in their current drive\subdirectory location. The file description will be placed in either the main or conference upload directory listing - unless you preface the description with a "/". Note: The sysop does NOT see Ascii uploads sent to his board. He will see all Ascii downloads however. Note: Callers using TRS hardware may generate a 'Short Block' error on the FIRST block when trying to upload a file to a PCBoard system. This is normal and will be properly handled by the code to allow the upload to continue. [V]iew Settings - Displays the callers current settings, including caller number, conference registration information, security level, number of uploads and downloads, transfer protocol, last message number read, number of active messages, and the next message number of that message base. If the caller is in novice mode, the program will pause after displaying the settings information to insure the caller gets a chance to review the information before the main menu over-writes it. 13 - 13 PCBoard Chapter 13 December 22, 1985 [W]rite User Info - Allows the user to alter their data base information - including their password. If you set the update flag in the PCBoard.DAT file to allow users to update all of their information, they will be able to change their City and State, Password, and two phone number entries. If you have set the flag to 'no', they will only be able to update their password. Callers who wish to alter their transfer protocol should use the [T] command. [X]Expert Mode - Allows the caller to toggle between novice and expert mode. The only difference being that in expert mode, the main board menu is not displayed. [Y]our Personal Mail - Allows the caller to scan the current message base for mail addressed to them or left by them. [Z]ippy DIR Scan - This function allows the caller to scan the file directories for a matching text string of up to 20 characters in length. The caller is asked to enter the text they wish to search for followed by the directories to be scanned. They can stack the [A] command at the main prompt line with the [Z] command if desired. (i.e. Z A or Z;A) The program will search the directories requested for matching text - irreguardless of the case of the text that the user enters. For example, if the user enters the word "printer", the program will display a match on all words which have "printer" in them - such as "Printer", "prinTER", etc. 13 - 14 PCBoard Chapter 14 December 22, 1985 T I P S O N R U N N I N G T H E B O A R D ----------------------------------------------------- Here are some additional tips for running the board: 1. If your screen clears while waiting for a call and you wish to recall it up - simply press a key. 2. The [Crtl-K] to Abort command during a system page will only work for the remote caller. If you request a sysop page in local mode, a [Ctrl-K] pressed at your keyboard will have no effect. 3. The 'Caller In' Alarm will sound your system speaker when a carrier is detected and again if the caller logs on into the system. It is also used throughout the program to indicate to you that the caller has performed an invalid function, made an erroneous request, or attempted to violate one of the board's security restrictions. NOTE: The caller gets all the beeps - even if the (ALRM) is toggled off. If your callers complain, tell them to filter out the chr$(7) character using their software program. 4. The default mode for the local sysop is color off and expert off. If you wish to switch to expert or graphics, use the "X" and "M" commands once you have logged on. These values will be saved to disk for all future calls until modified by you. 5. The default transfer protocol for the sysop is always "None". If you specify a type during that call, the value is saved to disk. 6. Several 'sysop' functions are hardcoded to only allow the actual sysop - the person logging on locally with the [Esc] key or remotely with the two sysop passwords - to actually perform some functions. For example, only "The Sysop" is automatically granted access to all conferences. If you grant sysop privileges to another person, they will not have all the privileges you maintain unless you allow them to use your 2 sysop passwords. 7. We have tried to provide for positive error trapping on some of the new PATH and BASICA features. 8. In most places the program will allow the use of either the space or the semi-colon as the stacked command delineator. 9. The stacked commands which are allowed are: Note: The [Space] can be used in place of the semi-colon below. B;x for bulletin scan (multiple numbers allowed) D;<filename>;<protocol> for downloading a file F;x for file listings (multiple numbers allowed) H;x for help (the 'x' is the function letter for help wanted) J;x for joining a conference K;x for killing a message L;A for scanning all DIRs (program will ask for the filename) N;A for scanning all DIRs (program will ask for the date) P;x for setting page length 14 - 1 PCBoard Chapter 14 December 22, 1985 Q;x for quick message scan R;x for reading messages T;x for protocol type where 'x' is X,C,A,or N U;<filename>;<protocol> for uploading a file Z;A for scanning all DIRs (program will ask for text to scan for) 10. Program defaults are provided for most user prompts. Please keep track of caller preference for future prompt modification(s). 11. You can press your [Home] key at any point in the program for function key help. Press [End] to restore the 24th and 25th lines. The lines will automatically return to their proper display if you forget to reset them. You can also use the [PgDn] key to display the additional user information available. 12. Use the [F6] function key to perform an on-line registration or update of a caller. If the caller is in the data base, you will be asked to update their information - after which they will be re- logged back onto the system at the main menu with their new level. If you do not wish to change their data base information, just press [C/R] to skip the item. Usually the only two items you will be modifying is their security level and conference registration information. If the user is not registered in the data base, you will be asked to complete an entire registration. Make sure you have the password the user wishes to use before selecting this option!!! Once complete, the user will be logged back onto the system at the main menu. CAUTION: DO NOT perform more than one on-line update of a caller per session. If you do, you may induce erroneous entries in your user's file in other than the caller's record. When updating information in the user's file, if you just press your [C/R], the caller's data will remain unchanged. To enter conference registration information, enter the number(s) the user is registered in. (i.e. "12 ", "246", etc.) If you wish to 'blank out' a field, press your space bar - then press return. For example, lets say you have two conferences and three registered callers - Sam, Bill and Joe. You want Sam registered in both conferences, Bill in number 1, and Joe in number 2. For Sam, the conference registration information to be entered would be "12 " or "21 " if you please! Bill's entry would be "1 " and Joe's would be "2 ". Since the program is simply looking for a match on any of the characters entered, they can be placed in any order desired. CAUTION: The entries in the CNAMES file must be in the proper order however. Failure to place them in proper order will result in a caller joining the wrong conference. 13. Be sure and use the alignment pattern supplied with the 'DIR' file listings. It is imperative that the dates appear in the columns shown in the samples for the date search to work properly inside the program!! 14 - 2 PCBoard Chapter 14 December 22, 1985 NOTE: Your file names MUST appear as a single word with a period separating the prefix and suffix of the filename! You can not have the filename extension separated from the filename prefix in columns 10-12 as is presently done by many sysops. If you filenames are split up in this manner, the [L]ocate command will NOT function properly! Follow the template(s) provided when building your directory listings! 14. The sysop, when logging onto the system, will only see the various 'NEWS' files if he is in novice mode. 15. The sysop can [P]rotect and [U]nprotect messages as they are being read. The "More - " prompt will always display the appropriate choice available. After toggling a message from protected mode to unprotected mode or visa versa, the message will be re-displayed. 16. When logging on in local mode as a user and you forgot what the user's password is - simply press [PgDn] and the program will display the password of the caller you have entered at the "first name" prompt. 17. DO NOT perform multiple [F6] on-line user registrations during a single call. This may cause errors to be created inside the user's data base which will cause pointers to be misplaced, etc. 18. The program checks for the current date of the BLT and xBLT files when a caller logs onto the system. If the files have been physically updated since their last call, the user will be displayed a message that the bulletins on the board have been updated. These displays are shown just before the caller is given the "Check your mail" prompt, and also just before the "View other conference members" prompt. This was done so that the message would be displayed at a logical point in the program which would not slow down it's operation. 19. In order to facilitate the use of external program call analyzers, the code provides an additional file on disk in the '\MAIN' subdirectory which simply stores information about completed downloads - including filename, transfer protocol used, and total number of block errors. This file can be analyzed much more quickly than the complete caller's log. It should be purged periodically if it is not used. The name of the file created is DOWNLOAD.TXT. 14 - 3 PCBoard Chapter 15 December 22, 1985 Q U E S T I O N S A N D A N S W E R S ------------------------------------------- Question: "I get an 'Error 0 in Line 1020 or 1030." Answer: Your message base is corrupted. Repack and insure the file has been properly converted. If it is a conference message base - insure packing has been done by re-naming the file as the main message base - then repack - then rename back to the conference file name. In some cases, you may still have one bad message in your message base which is causing a problem. I will be releasing an enhanced message pack program just for the purpose of trying to repack a badly damaged message base. This program will be separate from PCBoard and will only be needed in those cases where you may have experienced a disk error which has badly corrupted your message base(s) - or when trying to convert an RBBS message base to PCBoard which has bad message blocks in it. Question: "I get a 'String Corrupt Error'." Answer: Your message base or configuration is incorrect. Repack and thoroughly recheck your configuration. You may also have too many conferences defined for the program to handle. It is recommended that you do not exceed 5 active conferences. Please do not call in a 'bug' if you have more than 5 active conferences and you get the above error when jumping around between conferences. We strongly recommend that you limit the number of active conferences to 3. Trying to support more than this number is not doing your callers justice. Question: "I can't get my Hayes 1200 to answer the phone without garbage!" Answer: You may have not included the 'X1' code in the modem open or initialization string. Therefore, the modem is not responding with "CONNECT 1200" when a caller connects and the code thinks the caller is at 300 baud. Question: "Do you have message file and/or user file conversion program(s) to convert from RBBS to PCBoard format?" Answer: No, we will not support any conversion programs - nor will we be responsible for any that are posted on our board or elsewhere. It is the responsibility of the user to correctly convert any and all files they wish to use with PCBoard. Please note that the 'Error 0' and 'String Corrupt' errors are primarily due to improperly converted message bases and we will NOT respond to any questions concerning their proper conversion or problems you are having getting PCBoard to run because of these errors. PCBoard has been set up properly by many users without experiencing these two errors. Question: "When selecting some functions after logging on in local mode as either a user or the Sysop, I get a message saying 'Selection not Available.' Am I doing something wrong?" Answer: No, it means the selection is simply not available in local mode since it would cause an error if the program actually tried to perform the function you have requested. Examples of this are an Xmodem download, exit to remote, or file upload. 15 - 1 PCBoard Chapter 15 December 22, 1985 Question: "My code works fine in local mode, but won't answer the phone." Answer: You may not have pin 22 active on your modem. You MUST have pin 22 active and supported by the modem for the code to work. All 1200 baud Hayes modems, the new Courier 2400, and most Multi-Tech and Racal Vadic modems will work. You must have the switch settings on your modem set so that carrier detect is false and data terminal ready is false. These two items are handled by the software. Failure to have these two switches set properly will cause the program to either not run or run improperly - usually not hanging up the phone when the caller tries to logoff. Question: "On returning from DOS from remote, I get error messages and my machine locks up!" Answer: Most likely you tried to return to the board by typing 'EXIT' in the wrong drive\subdirectory location! Place a statement in the beginning of BOARD.BAT which forces you back to your default drive and subdirectory location before recalling PCBoard. Question: "I delete my CALLERS file from outside the code. Then when I re-enter the program, I get an error message!" Answer: I strongly recommend that you do NOT delete the caller's log file from outside the code. The program is structured so that a new caller's log header is written when deleting the log from inside the code. You should use this feature of the program to delete your caller log - don't do it outside the program. The program has been error trapped to eliminate this problem. However, if you need to archive your file, do so outside the program - then log on and use the # 2 [D]elete caller file function. In clearing the file in this manner, a new file header block is written to the file indicating when the file was initiated. Question: "My phone won't hang up!" Answer: Your pin 20, which controls the DTR signal, may not be active. Question: "The [L]ocate command will not work on my system!" Answer: You have not properly configured your file directory listings in accordance with this documentation. You must have a period between the filename prefix and suffix. Question: "I have a ten page NEWUSER file and my callers are getting kicked of the system before they can read it!" Answer: This code was designed to provide FAST system execution and quick caller on and off the system. If you need a 10 page NEWUSER file - please DO NOT use this code - it will give it a bad name!! The user must be able to get past the newuser welcome AND registration in 5 minutes or less. If you make it longer than that - they will always be logged off before they can even get on the system. This code WILL NOT be modified to support a longer access time. Please, do your callers a favor and cut the BS... Question: "I keep hitting the wrong function key and log people off when I really mean to go into chat mode!" Answer: Type more carefully! The position of the function keys will not 15 - 2 PCBoard Chapter 15 December 22, 1985 be altered. Question: "I can not get the remote DOS function (# 9) to work properly." Answer: Most likely your BOARD.DAT and REMOTE.SYS files are not properly configured, or you have improperly named them. First, there must be two files - REMOTE.SYS (which will be renamed to REMOTE.BAT by the program just before you exit to DOS.) - and a file called BOARD.BAT - which is the interactive batch file used to initialize the board. I have included three files in the PCBSUPxx.ARC file which are the ones used by this board for the function to work properly. Review those for suggestions on how to configure yours. Also, the file COMMAND.COM must be available on the default drive before you exit. This file is needed to properly over-lay the current COMMAND.COM on exiting. Question: "How do I set the switches on my Hayes to work properly?" Answer: Set them according to the documentation provided in chapter 4 of this manual. Similar switch settings should be used on other compatible modems. Question: "Sometimes the board seems to loose a caller's security level when logging on and assigns them the wrong time, or it sometimes seems to loose track of their last message read!" Answer: We are aware of the problem(s) that do not seem to have a pattern which are associated with the USER's file. At this point we are not sure what can cause this bug. Keep an eye on it and report any documented problems to us. It has been shown that by performing multiple [F6] on-line registrations during a single call cause generate similar errors. Therefore, do not perform more than a single [F6] update during the caller's period on the system Question: "A user logs on and gets assigned a time allocation of 10 minutes! I do not have such an entry in my PWRD file!" Answer: The program was not able to find an exact match on the security level you assigned the caller and one in the PWRD file. Therefore, the program defaulted to 10 minutes total at that point. Edit your PWRD's file and make sure there is an entry in the file corresponding to each security level you have assigned to your users. Question: "I am using a Hayes internal and can't get the code to work properly!" Answer: You may have a problem with your DTR configuration on the card. Check to make sure that the DTR jumper is properly set. Also make sure the S10 register is set to about 8-10. Question: "I get an Error # 58 when doing a message repack!" Answer: You may have an external DOS function affecting the program's operation - including the use of a DOS 3.1 SUBST command or the use of DPATH or FileFacility. Be sure these are not causing a conflict with the code. Question: "My caller's log shows a 'Fatal Crash: Err # xx in line XXXX'- but my board is still running!" Answer: The file (or actually absence of it) ENDPCB, which is created 15 - 3 PCBoard Chapter 15 December 22, 1985 ONLY if the program is exited normally, was not created because of the error when the code dropped out to the operating system. Since you had properly created the BOARD.BAT file with the correct logic for such an event, your board immediately recycled as it should. If this happens, please report the error # and line number to us for review. Question: "PCBoard does not agree with what DOS says my disk 'free' space is when running under DoubleDos!" Answer: DoubleDos has a problem! Their code does not always properly keep track of disk free space. As a suggestion, try increasing the size of your DoubleDos partition to correct the problem. Please be aware that PCBoard will ALWAYS give you the actual amount of free space on your disk!! Question: "When doing a file upload, the board says "File exists. Over- write it?" - when I say yes - it comes back with a software error # 53 in line 7120". Answer: Most probably you have a duplicate file somewhere that the program itself is not locating - but that another resident program is "finding" for the code - like File Facility or DPATH. Be sure neither of these is affecting the board's code. Question: "When reading messages - whether local or remote - I never get the "Message Received - Kill it now prompt" - How come my callers get it but I don't?" Answer: The code is set up so that anyone with sysop privileges can perform multiple functions on a message - such as protect or unprotect it, reply to it, etc. Because of this, the program always gives someone with sysop privileges the "More:" command line prompt rather than the "Kill it now" prompt. This allows them to do several things to one message if desired. Question: "How can I gain access to the Salt Air boards?" Answer: To gain access to the public Salt Air Board at (801) 266-0328, you must send your registration information - including first and last name, phone numbers, and password desired - plus a $20.00 yearly access fee to: Fred Clark P.O. Box 71365 Murray, UT 84107 Your registration will be processed and you will be placed in the user's file on the main board. To gain access to the PCBoard sysop's only board at (801) 266-0329, you must first follow the steps indicated above. Next, you must find a sysop who is currently registered on the board to 'sponsor' you. We do not maintain a list of registered sysops for public distribution. Through contact with other PCBoard operations, you will surely find some who are registered here on the Salt Air BBS system. Newest releases of PCBoard code are always available to registered callers on either board. You do not have to be registered on the sysop's only board to have access to the most current version of the code. 15 - 4 PCBoard Chapter 15 December 22, 1985 Question: "Why are there so many releases of PCBoard?" Answer: Our policy has always been to enhance the code according to the needs and wishes of the sysops who are running it. Likewise, if we are made aware of any program bugs or problems, they are usually addressed immediately. As soon as a bug is fixed and/or enhancement made, we release a new version or dated version. Because the code has been expanding rapidly to support many new features - there have been a lot of new releases. However, the code is reaching a rather stable point in it's development. As a result, fewer releases can be expected. Question: "Can I re-distribute the code to others?" Answer: Yes - by all means. Be prepared however to supply some level of support to them if you do - especially when they are initially configuring their systems for operation. Question: "What files should I protect and how?" Answer: You should at LEAST protect PCBOARD.DAT from being downloaded by anyone - including yourself! Since this file contains information which would allow a caller to gain access to your system as you, you should include it in your FSEC file. Optionally, you can exclude the board's default drive location from the download path string. This will prevent anyone from getting it - including you. Question: "What is the difference between CRC Xmodem and Ymodem CRC transfers - and why do Ymodem ones appear so slow?" Answer: Ymodem transfers use 'blocks' of data that are 1024 bytes long rather than 128 bytes long like Xmodem does. Since it takes longer to send one block - the transfer 'appears' to take longer. In reality - the time to do a file transfer using Ymodem is normally less than Xmodem - since less time it spent doing the 'ACK' procedure (block acknowledgement). However, Ymodem is best used on larger files and clean telephone lines. Xmodem is best for small files and/or 'dirty' lines. The reasons being that if it is necessary to resend a block, it is quicker to send a smaller block than a larger one. Also, files transferred using Ymodem will 'grow' to the next even interval of 1024K size - meaning you may spend more time transferring than needed. Rest assured however - that in either case - the file will be transferred in tact and will only be different in size 'appearance' - not functionality. 15 - 5 PCBoard Chapter 16 December 22, 1985 F I L E F O R M A T S U S E D ----------------------------------- Below is the format used by the software to store the user information. If you are planning on converting an RBBS user file to the format indicated - be sure and follow the format indicated exactly!! PCBoard uses a user record length of 134 bytes instead of 128 bytes as RBBS does. Be sure and pad for spaces in your conversion process. Start Pos/ Stored Length Format Description ---------- ------ -------------------------------------------------- 1,25 Ascii First and Last Name 26,24 Ascii City and State 50,12 Ascii Password 62,13 Ascii Business/Data Phone Number 75,13 Ascii Home/Voice Phone Number 88,8 Ascii Last Date on System (in mm-dd-yy format) 96,5 Ascii Last Logon Time (in hh:mm format) 101,1 Ascii Expert Mode - "Y" or "N" 102,1 Ascii Protocol - "X", "C", "A", or "N" where "X"=Checksum Xmodem "C"=CRC Xmodem "A"=Ascii "N"=None specified 103,3 Ascii Conferences Registered In - "1 ", "35 ", etc. where "1 " means just conference #1, "35 " means conference #'s 3 and 5 106,1 Ascii Last Conference Left - "1", "2", etc. 107,1 Ascii Auto Rejoin Last Conference "Y" or "N" 108,6 Ascii Last Date Looked at a Directory (in yymmdd format) 114,2 MKI$ Security Level 116,2 MKI$ Number of Times on System 118,2 MKI$ Page Length 120,2 MKI$ Last Message Number Read in Main Board 122,2 MKI$ Last Message Number Read in 1st Conference 124,2 MKI$ Last Message Number Read in 2nd Conference 126,2 MKI$ Last Message Number Read in 3rd Conference 128,2 MKI$ Number of Uploads 130,2 MKI$ Number of Downloads 132,2 MKI$ Elapsed Time on System on Last Date Called 134,1 Ascii Positive Delete Flag to Delete User During Repack PCBoard only allows 1 word passwords of 12 characters or less in length. If you have users who have a two part password with a space between the individual parts, you will need to convert it to a one word password which you must tell your caller(s) you are going to do. We recommend that you leave messages for callers so affected so they can change their password before putting PCBoard up on line. If you fail to do this, those callers with two part passwords will be denied access to the system!! 16 - 1 PCBoard Chapter 16 December 22, 1985 Following is the format used to store messages in the system. If you are planning on converting an RBBS message file to the format indicated - be sure and follow the format indicated exactly!! PCBoard uses a message file which is comprised of records 128 bytes in length. It uses a single message 'header' block for each message file - followed by the actual messages. The first header block is used to store sysop profile information and message numbering information. Failure to properly initialize this file may lock up your machine! The first 128 byte block of each message base contains the following information: Start Pos/ Stored Length Format Description ---------- ------ -------------------------------------------------- 1,8 Ascii Number of Last Message Left 9,8 Ascii Number of Last Caller on System 17,4 Ascii Baud Rate at Which Sysop exited to DOS 21,2 Ascii Page Bell On/Off (-1 or 0) 23,2 Ascii Caller Alarm On/Off (-1 or 0) 25,2 Ascii Printer On/Off (-1 or 0) 27,2 Ascii Screen Blank On/Off (-1 or 0) 29,8 Ascii Last Message Number Read by Sysop 37,1 Ascii Sysop's Transfer Protocol Default 38,1 Ascii Sysop's Expert/Novice Mode 39,2 MKI$ Sysop's Graphics Mode 41,6 Ascii Sysop's last directory look (yymmdd format) 50,27 Ascii Name of caller who exited to DOS + 2 spaces 77,15 Ascii Display 'First Name' of caller 92,2 Ascii Graphics mode of above caller (-1 or 0) 94,1 Ascii Protocol of above caller (X, C, A or N) 95,2 Ascii Expert/Novice mode of above caller (-1 or 0) 97,12 Ascii Remote password needed to re-enter program 109,2 Ascii Sysop gets system next (-1 or 0) Following the first block, are blocks containing the various messages. The first block of each message must be as follows. The first 128 byte block of each message contains the following information: Start Pos/ Stored Length Format Description ---------- ------ -------------------------------------------------- 1,1 Ascii Protected/Unprotected Flag (* or blank) 2,7 Ascii Message Number 9,8 Ascii Date of Message (in mm-dd-yy format) 17,5 Ascii Time of Message (in hh:mm format) 22,25 Ascii Who the Message is For 47,25 Ascii Who the Message is From 72,25 Ascii Subject of the Message 97,12 Ascii Message Password (if any or ^^ for RBBS ^READ^) 109,8 Ascii Reference Message Number 117,6 Ascii Number of 128 byte blocks in Message 123,1 Ascii Flag for Message Status (chr$(225) or chr$(226)) 124,5 Not Used 16 - 2 PCBoard Chapter 16 December 22, 1985 RBBS USERS: You must convert the "^READ^" password to "^^"+SPACE$(10) during the conversion or all previously protected messages will NO longer be private running under the new code! CAUTION: If you are not capable of writing a conversion program for your present message file(s), it is strongly recommended that you begin your message base from scratch! After entering one message in your new system, repack the message base to reset all message number pointers properly (i.e. From '0' to '1'). End of PCBoard Documentation 16 - 3